From: Ian Kent <raven@themaw.net>
To: Andrew Morton <akpm@osdl.org>
Cc: autofs@linux.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] autofs4 needs to force fail return revalidate
Date: Fri, 23 Jun 2006 14:43:59 +0800 (WST) [thread overview]
Message-ID: <Pine.LNX.4.64.0606231434480.15807@raven.themaw.net> (raw)
In-Reply-To: <20060622213050.fc753e91.akpm@osdl.org>
On Thu, 22 Jun 2006, Andrew Morton wrote:
> On Fri, 23 Jun 2006 12:14:09 +0800 (WST)
> Ian Kent <raven@themaw.net> wrote:
>
> > >
> > > Also, did you consider broadening the ->d_revalidate() semantics? It
> > > appears that all implementations return 0 or 1. You could teach the VFS to
> > > also recognise and act upon a -ve return value, and do this trickery within
> > > the autofs d_revalidate(), perhaps?
> > >
> >
> > Yep and I've now done this.
> > I think this is in fact the only way to do it.
>
> Below is the combined patch for reviewing purposes.
>
> Removing that __always_inline saves 30-odd bytes. I suspect that removing
> it would be a performance loss in this case. But I'll make it just
> `inline' because __always_inline is peculiar, and people will wonder what's
> special about this function.
>
Thanks Andrew.
The combined diff is exactly what I'm trying to achieve.
I marked the function __always_inline because several other functions
that appear to be frequently called from this code path are also declared
this way. Hopefully someone with more experience of this area of the VFS
will recommend the best choice.
Ian
next prev parent reply other threads:[~2006-06-23 6:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 6:18 [PATCH] autofs4 needs to force fail return revalidate Ian Kent
2006-06-21 6:39 ` Andrew Morton
2006-06-21 13:07 ` Ian Kent
2006-06-21 13:39 ` Ian Kent
2006-06-23 4:14 ` Ian Kent
2006-06-23 4:30 ` Andrew Morton
2006-06-23 6:43 ` Ian Kent [this message]
2006-07-10 10:24 ` Andrew Morton
2006-07-10 16:23 ` [autofs] " Ian Kent
2006-06-21 12:25 ` Al Viro
2006-06-21 13:05 ` Ian Kent
2006-06-21 13:37 ` [autofs] " Jeff Moyer
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=Pine.LNX.4.64.0606231434480.15807@raven.themaw.net \
--to=raven@themaw.net \
--cc=akpm@osdl.org \
--cc=autofs@linux.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).