public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Paul Menage <pmenage@ensim.com>
Cc: Andi Kleen <ak@suse.de>, Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org, lse-tech@sourceforge.net
Subject: Re: [Lse-tech] Re: [PATCH] New dcache / inode hash tuning patch
Date: Fri, 28 Feb 2003 11:40:56 +0100	[thread overview]
Message-ID: <20030228104056.GA1647@wotan.suse.de> (raw)
In-Reply-To: <E18ohjj-0005ls-00@pmenage-dt.ensim.com>

On Fri, Feb 28, 2003 at 02:27:27AM -0800, Paul Menage wrote:
> >But for lookup walking even one cache line - the one containing d_hash -
> >should be needed. Unless d_hash is unlucky enough to cross a cache
> >line for its two members ... but I doubt that.
> 
> No, but on a 32-byte cache line system, d_parent, d_hash and d_name are
> all on different cache lines, and they're used when checking each entry.

... and dcache RCU checks d_bucket and d_move_count too in the hash 
walking loop.


> On 64-byte systems, d_parent and d_hash will be on the same line, but
> d_name is still on a separate line and d_name.hash gets checked before
> d_parent. So bringing these three fields on to the same cacheline
> would theoretically be a win.

Ok you're right. Optimizing the layout a bit would be probably a good 
idea. I won't include it in the hash patchkit for now to not do too
many things with the same patch.

-Andi

  reply	other threads:[~2003-02-28 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030226164904.GA21342@wotan.suse.de.suse.lists.linux.kernel>
     [not found] ` <b3m5sd$1ad$1@penguin.transmeta.com.suse.lists.linux.kernel>
2003-02-28  8:34   ` [PATCH] New dcache / inode hash tuning patch Andi Kleen
2003-02-28 10:27     ` [Lse-tech] " Paul Menage
2003-02-28 10:40       ` Andi Kleen [this message]
2003-02-28 18:47     ` Linus Torvalds
2003-02-28 18:59       ` Andi Kleen
2003-03-01  0:49         ` Jan Harkes
2003-03-01  1:17           ` Andi Kleen
2003-03-01  4:31             ` Ed Tomlinson
2003-03-01  9:08               ` Andi Kleen
2003-03-01 12:34                 ` Ed Tomlinson
2003-03-01 18:34               ` Linus Torvalds

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=20030228104056.GA1647@wotan.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@sourceforge.net \
    --cc=pmenage@ensim.com \
    --cc=torvalds@transmeta.com \
    /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