Re: [RFC 4/4] bdev: extend bdev inode with it's own super_block

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Luis Chamberlain <mcgrof@xxxxxxxxxx>
Subject: Re: [RFC 4/4] bdev: extend bdev inode with it's own super_block
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 8 Jun 2023 06:50:48 -0700
Cc: hch@xxxxxxxxxxxxx, djwong@xxxxxxxxxx, dchinner@xxxxxxxxxx, kbusch@xxxxxxxxxx, willy@xxxxxxxxxxxxx, hare@xxxxxxx, ritesh.list@xxxxxxxxx, rgoldwyn@xxxxxxxx, jack@xxxxxxx, patches@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, p.raghav@xxxxxxxxxxx, da.gomez@xxxxxxxxxxx, rohan.puri@xxxxxxxxxxx, rpuri.linux@xxxxxxxxx, corbet@xxxxxxx, jake@xxxxxxx
In-reply-to: <20230608032404.1887046-5-mcgrof@kernel.org>

On Wed, Jun 07, 2023 at 08:24:04PM -0700, Luis Chamberlain wrote:
> each block device corresponds to one inode on that super_block. This
> implicates sharing one aops operation though,

No, it does not.

References:
- [RFC 0/4] bdev: allow buffer-head & iomap aops to co-exist
  - From: Luis Chamberlain
- [RFC 4/4] bdev: extend bdev inode with it's own super_block
  - From: Luis Chamberlain

Prev by Date: Re: [RFC 4/4] bdev: extend bdev inode with it's own super_block
Next by Date: Re: [RFC 1/4] bdev: replace export of blockdev_superblock with BDEVFS_MAGIC
Previous by thread: Re: [RFC 4/4] bdev: extend bdev inode with it's own super_block
Next by thread: [RFC 1/4] bdev: replace export of blockdev_superblock with BDEVFS_MAGIC
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux