From: Andi Kleen <andi@firstfloor.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
viro@zeniv.linux.org.uk, eparis@redhat.com,
linux-audit@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 00/10] vfs: getname/putname overhaul
Date: Sat, 8 Sep 2012 05:08:50 +0200 [thread overview]
Message-ID: <20120908030850.GH16230@one.firstfloor.org> (raw)
In-Reply-To: <20120907205418.244bd797@corrin.poochiereds.net>
On Fri, Sep 07, 2012 at 08:54:18PM -0400, Jeff Layton wrote:
> On Fri, 07 Sep 2012 14:26:56 -0700
> Andi Kleen <andi@firstfloor.org> wrote:
>
> > Jeff Layton <jlayton@redhat.com> writes:
> >
> > > This patchset is a first pass at overhauling the getname/putname
> > > interface to use a struct. The idea here is to add a new getname_info
> > > struct that allow us to pass around some auxillary info along with
> > > the string that getname() returns.
> >
> > Couldn't you just use some of the free pointers in struct page?
> > (lru etc.)
> >
> > -Andi
> >
>
> We could do that if these were page allocations. They're not, however.
> __getname() does a PATH_MAX size allocation out of a slabcache. I get
Ok I suppose slab is faster. In this case it's better to track
separately I agree.
-Andi
next prev parent reply other threads:[~2012-09-08 3:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 13:37 [PATCH v1 00/10] vfs: getname/putname overhaul Jeff Layton
2012-09-07 13:37 ` [PATCH v1 01/10] vfs: allocate page instead of names_cache buffer in mount_block_root Jeff Layton
2012-09-07 13:37 ` [PATCH v1 02/10] vfs: make dir_name arg to do_mount a const char * Jeff Layton
2012-09-07 13:37 ` [PATCH v1 03/10] acct: constify the name arg to acct_on Jeff Layton
2012-09-07 13:37 ` Jeff Layton
2012-09-07 13:37 ` [PATCH v1 04/10] vfs: define getname_info struct and have getname() return it Jeff Layton
2012-09-07 13:38 ` [PATCH v1 05/10] audit: allow audit code to satisfy getname requests from its names_list Jeff Layton
2012-09-07 13:38 ` [PATCH v1 06/10] vfs: turn do_path_lookup into wrapper around getname_info variant Jeff Layton
2012-09-07 13:38 ` [PATCH v1 07/10] vfs: make path_openat take a getname_info pointer Jeff Layton
2012-09-07 13:38 ` [PATCH v1 08/10] audit: make audit_inode take getname_info Jeff Layton
2012-09-07 13:38 ` [PATCH v1 09/10] vfs: embed getname_info inside of names_cache allocation if possible Jeff Layton
2012-09-07 13:38 ` [PATCH v1 10/10] vfs: unexport getname and putname symbols Jeff Layton
2012-09-07 21:26 ` [PATCH v1 00/10] vfs: getname/putname overhaul Andi Kleen
2012-09-08 0:54 ` Jeff Layton
2012-09-08 3:08 ` Andi Kleen [this message]
2012-09-08 11:24 ` Jeff Layton
2012-09-08 11:24 ` Jeff Layton
2012-09-08 15:38 ` Andi Kleen
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=20120908030850.GH16230@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=eparis@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.