From: Yu Kuai <yukuai1@huaweicloud.com>
To: Christoph Hellwig <hch@infradead.org>, Jan Kara <jack@suse.cz>
Cc: hoeppner@linux.ibm.com, vigneshr@ti.com, yi.zhang@huawei.com,
clm@fb.com, adilger.kernel@dilger.ca, miquel.raynal@bootlin.com,
agordeev@linux.ibm.com, linux-s390@vger.kernel.org,
linux-nilfs@vger.kernel.org, linux-scsi@vger.kernel.org,
richard@nod.at, willy@infradead.org,
linux-bcachefs@vger.kernel.org, xen-devel@lists.xenproject.org,
linux-ext4@vger.kernel.org, Yu Kuai <yukuai1@huaweicloud.com>,
jejb@linux.ibm.com, p.raghav@samsung.com, gor@linux.ibm.com,
hca@linux.ibm.com, joern@lazybastard.org, josef@toxicpanda.com,
colyli@suse.de, linux-block@vger.kernel.org,
linux-bcache@vger.kernel.org, viro@zeniv.linux.org.uk,
"yukuai \(C\)" <yukuai3@huawei.com>,
dsterba@suse.com, konishi.ryusuke@gmail.com, axboe@kernel.dk,
brauner@kernel.org, tytso@mit.edu, martin.petersen@oracle.com,
nico@fluxnic.net, yangerkun@huawei.com,
linux-kernel@vger.kernel.org, kent.overstreet@gmail.com,
hare@suse.de, jack@suse.com, linux-fsdevel@vger.kernel.org,
linux-mtd@lists.infradead.org, akpm@linux-foundati on.org,
roger.pau@citrix.com, linux-erofs@lists.ozlabs.org,
linux-btrfs@vger.kernel.org, sth@linux.ibm.com
Subject: Re: [PATCH RFC v3 for-6.8/block 04/17] mtd: block2mtd: use bdev apis
Date: Fri, 5 Jan 2024 18:31:53 +0800 [thread overview]
Message-ID: <28237ec3-c3c1-1f0c-5250-04a88845d4a6@huaweicloud.com> (raw)
In-Reply-To: <ZZedSYAedA05Oex2@infradead.org>
Hi,
在 2024/01/05 14:10, Christoph Hellwig 写道:
> On Thu, Jan 04, 2024 at 12:28:55PM +0100, Jan Kara wrote:
>> What do you think? Because when we are working with the folios it is rather
>> natural to use their mapping for dirty balancing?
>
> The real problem is that block2mtd pokes way to deep into block
> internals.
>
> I think the saviour here is Christians series to replace the bdev handle
> with a struct file, which will allow to use the normal file write path
> here and get rid of the entire layering volation.
Yes, looks like lots of patches from this set is not needed anymore.
I'll stop sending v4 and just send some patches that is not related to
'bd_inode' separately.
Thanks,
Kuai
>
> .
>
next prev parent reply other threads:[~2024-01-05 10:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 8:56 [PATCH RFC v3 for-6.8/block 00/17] block: don't access bd_inode directly from other modules Yu Kuai
2023-12-21 8:56 ` [PATCH RFC v3 for-6.8/block 01/17] block: add some bdev apis Yu Kuai
2023-12-21 8:56 ` [PATCH RFC v3 for-6.8/block 02/17] xen/blkback: use bdev api in xen_update_blkif_status() Yu Kuai
2024-01-04 11:06 ` Jan Kara
2024-01-04 12:19 ` Yu Kuai
2024-01-04 15:16 ` Jan Kara
2024-01-05 6:08 ` Christoph Hellwig
2023-12-21 8:56 ` [PATCH RFC v3 for-6.8/block 03/17] bcache: use bdev api in read_super() Yu Kuai
2023-12-21 8:56 ` [PATCH RFC v3 for-6.8/block 04/17] mtd: block2mtd: use bdev apis Yu Kuai
2024-01-04 11:28 ` Jan Kara
2024-01-04 12:22 ` Yu Kuai
2024-01-05 6:10 ` Christoph Hellwig
2024-01-05 10:31 ` Yu Kuai [this message]
2023-12-21 8:57 ` [PATCH RFC v3 for-6.8/block 05/17] s390/dasd: use bdev api in dasd_format() Yu Kuai
2023-12-21 8:57 ` [PATCH RFC v3 for-6.8/block 06/17] scsicam: use bdev api in scsi_bios_ptable() Yu Kuai
2023-12-21 8:57 ` [PATCH RFC v3 for-6.8/block 07/17] bcachefs: remove dead function bdev_sectors() Yu Kuai
2024-04-11 17:49 ` Kent Overstreet
2023-12-21 8:57 ` [PATCH RFC v3 for-6.8/block 08/17] bio: export bio_add_folio_nofail() Yu Kuai
2023-12-21 8:57 ` [PATCH RFC v3 for-6.8/block 09/17] btrfs: use bdev apis Yu Kuai
2023-12-23 17:31 ` Matthew Wilcox
2023-12-23 18:39 ` Kent Overstreet
2024-01-04 11:49 ` Jan Kara
2024-04-10 17:28 ` David Sterba
2023-12-21 8:57 ` [PATCH RFC v3 for-6.8/block 10/17] cramfs: use bdev apis in cramfs_blkdev_read() Yu Kuai
2023-12-21 8:58 ` [PATCH RFC v3 for-6.8/block 11/17] erofs: use bdev api Yu Kuai
2024-01-04 12:02 ` Jan Kara
2024-01-04 12:32 ` Yu Kuai
2024-01-05 4:43 ` Gao Xiang
2023-12-21 8:58 ` [PATCH RFC v3 for-6.8/block 12/17] nilfs2: use bdev api in nilfs_attach_log_writer() Yu Kuai
2023-12-21 14:54 ` Ryusuke Konishi
2023-12-21 8:58 ` [PATCH RFC v3 for-6.8/block 13/17] jbd2: use bdev apis Yu Kuai
2024-01-04 12:11 ` Jan Kara
2023-12-21 8:58 ` [PATCH RFC v3 for-6.8/block 14/17] buffer: add a new helper to read sb block Yu Kuai
2024-01-04 12:22 ` Jan Kara
2023-12-21 8:58 ` [PATCH RFC v3 for-6.8/block 15/17] ext4: use " Yu Kuai
2023-12-21 8:59 ` [PATCH RFC v3 for-6.8/block 16/17] ext4: remove block_device_ejected() Yu Kuai
2023-12-21 8:59 ` [PATCH RFC v3 for-6.8/block 17/17] ext4: use bdev apis Yu Kuai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28237ec3-c3c1-1f0c-5250-04a88845d4a6@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=adilger.kernel@dilger.ca \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundati \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=clm@fb.com \
--cc=colyli@suse.de \
--cc=dsterba@suse.com \
--cc=gor@linux.ibm.com \
--cc=hare@suse.de \
--cc=hca@linux.ibm.com \
--cc=hch@infradead.org \
--cc=hoeppner@linux.ibm.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=jejb@linux.ibm.com \
--cc=joern@lazybastard.org \
--cc=josef@toxicpanda.com \
--cc=kent.overstreet@gmail.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=miquel.raynal@bootlin.com \
--cc=nico@fluxnic.net \
--cc=p.raghav@samsung.com \
--cc=richard@nod.at \
--cc=tytso@mit.edu \
--cc=vigneshr@ti.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).