From: Christoph Hellwig <hch@infradead.org>
To: Ram Pai <linuxram@us.ibm.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH v2] vfs: optimization to /proc/<pid>/mountinfo patch
Date: Mon, 10 Mar 2008 03:10:46 -0400 [thread overview]
Message-ID: <20080310071046.GA23574@infradead.org> (raw)
In-Reply-To: <1205132015.15345.87.camel@ram.us.ibm.com>
On Sun, Mar 09, 2008 at 11:53:34PM -0700, Ram Pai wrote:
> 1) reports deleted inode in dentry_path() consistent with that in __d_path()
> 2) modified __d_path() to use prepend(), reducing the size of __d_path()
> 3) moved all the functionality that reports mount information in /proc under
> CONFIG_PROC_FS.
I think that latter one goes to far, mnt_id and mn_pdid are generally
useful information that should be generated unconditionally. That will
also get rid of most of the ifdef clutter introduced in this patch.
next prev parent reply other threads:[~2008-03-10 7:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 15:39 how to show propagation state for mounts Miklos Szeredi
2008-02-20 16:04 ` Al Viro
2008-02-20 16:27 ` Miklos Szeredi
2008-02-20 19:29 ` Ram Pai
2008-02-20 21:14 ` Al Viro
2008-02-20 21:35 ` Miklos Szeredi
2008-02-22 14:46 ` [rfc patch] " Miklos Szeredi
2008-03-05 19:25 ` Serge E. Hallyn
2008-03-05 19:34 ` Miklos Szeredi
2008-03-05 20:23 ` Ram Pai
2008-03-10 6:53 ` [RFC PATCH v2] vfs: optimization to /proc/<pid>/mountinfo patch Ram Pai
2008-03-10 7:10 ` Christoph Hellwig [this message]
2008-03-10 11:39 ` Miklos Szeredi
2008-02-20 16:31 ` how to show propagation state for mounts Matthew Wilcox
2008-02-20 19:42 ` Ram Pai
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=20080310071046.GA23574@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=miklos@szeredi.hu \
--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).