From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: herbert@13thfloor.at
Cc: trond.myklebust@fys.uio.no,
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: 08 Jul 2003 17:53:34 +0100 [thread overview]
Message-ID: <1057683213.5228.3.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030708164426.GB10004@www.13thfloor.at>
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.
next prev parent reply other threads:[~2003-07-08 16:42 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 [this message]
2003-07-08 17:06 ` Herbert Poetzl
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=1057683213.5228.3.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hannal@us.ibm.com \
--cc=herbert@13thfloor.at \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=trond.myklebust@fys.uio.no \
/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®