From: viro@parcelfarce.linux.theplanet.co.uk
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test6-mm2
Date: Thu, 2 Oct 2003 18:23:19 +0100 [thread overview]
Message-ID: <20031002172318.GF7665@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <16252.23200.511369.466054@laputa.namesys.com>
On Thu, Oct 02, 2003 at 09:04:32PM +0400, Nikita Danilov wrote:
> Andrew Morton writes:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test6/2.6.0-test6-mm2/
> >
> > . A large series of VFS patches from Al Viro which replace usage of
> > file->f_dentry->d_inode->i_mapping with the new file->f_mapping.
> >
> > This is mainly so we can get disk hot removal right.
>
> What consequences does this have for (out-of-the-tree) file systems,
> beyond s/->f_dentry->d_inode->i_mapping/->f_mapping/g ?
None. It only matters for block device inodes. Out-of-tree fs is free to
do whatever it does with inodes of regular files/directories/etc.
In quite a few cases you can cut down on dereferencing that way, but that's
covered by what you've mentioned.
If you take a look at the patchset you'll see
* change of method prototypes in block devices (aka "you don't need
to start with bdev = inode->i_bdev, you get it from arguments" - check RD1--RD6
and you'll see)
* a lot of places in mm/* that got aforementioned search-and-replace
treatment
* very few changes in fs code, most of them of the same variety (same
search-and-replace)
* couple of helper functions changed their prototypes:
generic_write_checks() lost "inode" argument
generic_osync_inode(), OTOH, got explicit address_space one.
That's it.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-10-02 17:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 9:23 2.6.0-test6-mm2 Andrew Morton
2003-10-02 13:37 ` 2.6.0-test6-mm2 Thomas Schlichter
2003-10-02 13:42 ` 2.6.0-test6-mm2 viro
2003-10-02 13:45 ` 2.6.0-test6-mm2 Robert Love
2003-10-02 13:45 ` 2.6.0-test6-mm2 Luiz Capitulino
2003-10-02 15:03 ` 2.6.0-test6-mm2 Andrew Morton
2003-10-02 18:29 ` 2.6.0-test6-mm2 Luiz Capitulino
2003-10-02 16:43 ` 2.6.0-test6-mm2 (compile statistics) John Cherry
2003-10-02 17:04 ` 2.6.0-test6-mm2 Nikita Danilov
2003-10-02 17:23 ` viro [this message]
2003-10-02 20:35 ` 2.6.0-test6-mm2 Bongani Hlope
2003-10-02 20:45 ` 2.6.0-test6-mm2 Chris Wright
2003-10-02 20:58 ` 2.6.0-test6-mm2 Bongani Hlope
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=20031002172318.GF7665@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=Nikita@Namesys.COM \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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