From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH 07/17] fs: Generic infrastructure for optional inode fields
Date: Fri, 2 May 2014 07:44:09 -0700 [thread overview]
Message-ID: <20140502144409.GB5902@infradead.org> (raw)
In-Reply-To: <1399036808-24521-8-git-send-email-jack@suse.cz>
On Fri, May 02, 2014 at 03:19:58PM +0200, Jan Kara wrote:
> There are parts of struct inode which are used only by a few filesystems
> (e.g. i_dquot pointers, i_mapping->private_list, ...). Thus all the
Why don't you move the private_list into the fs inode like you did
in the previous few patches and remove the references from the generic
code? This would involve some heavy lifting in buffer.c, but that's
long overdue anyway.
next prev parent reply other threads:[~2014-05-02 14:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 13:19 [PATCH 00/17] Shrink inode size Jan Kara
2014-05-02 13:19 ` [PATCH 01/17] fs: Remove i_devices from inode Jan Kara
2014-05-02 14:42 ` Christoph Hellwig
2014-05-20 15:28 ` Jan Kara
2014-05-02 13:19 ` [PATCH 02/17] fs: Save pointer in struct inode by better unioning Jan Kara
2014-05-02 13:19 ` [PATCH 03/17] hugetlbfs: Use own list instead of mapping->private_list Jan Kara
2014-05-02 13:19 ` [PATCH 04/17] aio: Use i_private instead of mapping->private_data Jan Kara
2014-05-02 13:19 ` [PATCH 05/17] virtio_balloon: Store mapping directly in balloon_dev_info Jan Kara
2014-05-02 13:19 ` [PATCH 06/17] fs: Don't store backing dev mapping in inode->i_mapping->private_data Jan Kara
2014-05-02 13:19 ` [PATCH 07/17] fs: Generic infrastructure for optional inode fields Jan Kara
2014-05-02 14:44 ` Christoph Hellwig [this message]
2014-05-02 19:44 ` Jan Kara
2014-05-02 13:19 ` [PATCH 08/17] fs: Convert i_data.private_list to use optional field infrastructure Jan Kara
2014-05-02 13:20 ` [PATCH 09/17] ext2: Use own optional list for metadata bhs Jan Kara
2014-05-02 13:20 ` [PATCH 10/17] udf: " Jan Kara
2014-05-02 13:20 ` [PATCH 11/17] affs: " Jan Kara
2014-05-02 13:20 ` [PATCH 12/17] bfs: " Jan Kara
2014-05-02 13:20 ` [PATCH 13/17] fat: " Jan Kara
2014-05-02 13:20 ` [PATCH 14/17] minix: " Jan Kara
2014-05-02 13:20 ` [PATCH 15/17] sysv: " Jan Kara
2014-05-02 13:20 ` [PATCH 16/17] ext4: " Jan Kara
2014-05-02 13:20 ` [PATCH 17/17] fs: Remove mapping->private_list Jan Kara
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=20140502144409.GB5902@infradead.org \
--to=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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 NNTP newsgroup(s).