From: Andrew Morton <akpm@digeo.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blockgroup_lock: hashed spinlocks for ext2 and ext3
Date: Mon, 14 Apr 2003 14:58:52 -0700 [thread overview]
Message-ID: <20030414145852.6beabadf.akpm@digeo.com> (raw)
In-Reply-To: <20030414214608.GA3392@wotan.suse.de>
Andi Kleen <ak@suse.de> wrote:
>
> >
> > And this hashed lock is not a per-cpu thing. (No locks are!) It just uses
> > NR_CPUS to decide how big the hash should be.
>
> Isn't that what the IBM kmalloc_per_cpu() was for ? (I think the patch
> was from Dipankar)
This is not a per-cpu data structure.
It is a hashed spinlock which uses NR_CPUS as a sizing hint.
prev parent reply other threads:[~2003-04-14 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200304131113.h3DBDvj2004773@hera.kernel.org>
2003-04-14 20:06 ` Andi Kleen
2003-04-14 21:38 ` Andrew Morton
2003-04-14 21:46 ` Andi Kleen
2003-04-14 21:58 ` Andrew Morton [this message]
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=20030414145852.6beabadf.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=ak@suse.de \
--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
all inboxes | Powered by JetHome®