From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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: Tue, 8 Jul 2003 17:00:35 +0200 [thread overview]
Message-ID: <16138.56467.342593.715679@charged.uio.no> (raw)
In-Reply-To: <1057673804.4357.27.camel@dhcp22.swansea.linux.org.uk>
>>>>> " " == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> I was a little suprised it went in, it never seemed a candidate
> for dealing with a stable tree, just optimisation stuff that is
> 2.5 material only
As you can see, I screwed up on the title, so I may have confused
you...
...but I do agree with your comment. The patch I meant to refer to
(see revised title) does not appear in the 2.5.x tree either.
Have we BTW been shown any numbers that support the alleged benefits?
I may have missed those...
Cheers,
Trond
next prev parent reply other threads:[~2003-07-08 14:47 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 ` Trond Myklebust [this message]
2003-07-08 15:20 ` [PATCH] Fastwalk: reduce cacheline bouncing of d_count (Changelog@1.1024.1.11) Alan Cox
2003-07-08 16:44 ` Herbert Poetzl
2003-07-08 16:53 ` Alan Cox
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=16138.56467.342593.715679@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--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®