mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	hannal@us.ibm.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux FSdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] Fastwalk: reduce cacheline bouncing of d_count (Changelog@1.1024.1.11)
Date: Tue, 8 Jul 2003 19:06:28 +0200	[thread overview]
Message-ID: <20030708170628.GA13593@www.13thfloor.at> (raw)
In-Reply-To: <1057683213.5228.3.camel@dhcp22.swansea.linux.org.uk>

On Tue, Jul 08, 2003 at 05:53:34PM +0100, Alan Cox wrote:
> On Maw, 2003-07-08 at 17:44, Herbert Poetzl wrote:
> > > Its no big problem to me since I can just back it out of -ac
> > 
> > just curious, because I use this patch since early 2.4.20,
> > are there any reasons to 'back it out of -ac' for you?
> > 
> > anyway I totally agree that the NFS issue pointed out by 
> > Trond should be addressed ...
> 
> Its high risk, its got bugs as Trond already showed and it only
> helps performance on giant SMP boxes. Its all risk and no
> reward. Quota updates get you working 32bit uid quota and
> the interactivity stuff helps all even tho its got some
> risk.

every change (if it's not a bugfix, and even those) bear
a risk, what I like about the fastwalk patch is not the
performance gain on giant SMP boxes, because I do not have
any (unfortunately ;) but the code change from ...

        if (path_init(pathname,  LOOKUP_PARENT, &nd))
                error = path_walk(pathname, &nd);

to
        error = path_lookup(pathname,  LOOKUP_PARENT, &nd);


and

        dentry = cached_lookup(nd->dentry, &this, 0);
        if (!dentry) {
                dentry = real_lookup(nd->dentry, &this, 0);
                err = PTR_ERR(dentry);
                if (IS_ERR(dentry))
                         break;
        }

to
	err = do_lookup(nd, &this, &next, &pinned, 0);


which (at least for me) is more read-/understandable ...

anyway, thanks for you answer,
Herbert


  reply	other threads:[~2003-07-08 16:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08 14:04 [PATCH] path_lookup for 2.4.20-pre4 (ChangeSet@1.587.10.71) Trond Myklebust
2003-07-08 14:16 ` Alan Cox
2003-07-08 15:00   ` [PATCH] Fastwalk: reduce cacheline bouncing of d_count (Changelog@1.1024.1.11) Trond Myklebust
2003-07-08 15:20     ` Alan Cox
2003-07-08 16:44       ` Herbert Poetzl
2003-07-08 16:53         ` Alan Cox
2003-07-08 17:06           ` Herbert Poetzl [this message]
2003-07-08 17:20             ` Matthew Wilcox
2003-07-08 17:42               ` Hanna Linder
2003-07-08 18:10                 ` Trond Myklebust
2003-07-08 18:19                   ` Hanna Linder
2003-07-08 19:26           ` Marcelo Tosatti
2003-07-08 19:24       ` Marcelo Tosatti
2003-07-08 16:20 ` [PATCH] path_lookup for 2.4.20-pre4 (ChangeSet@1.587.10.71) Jan Harkes
2003-07-08 16:41   ` [PATCH] Fastwalk: reduce cacheline bouncing of d_count (Changelog@1.1024.1.11) Trond Myklebust

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=20030708170628.GA13593@www.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hannal@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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

all inboxes | Powered by JetHome®