From: David Howells <dhowells@redhat.com>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Nick Piggin <npiggin@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch] generic rwsems
Date: Fri, 13 Apr 2007 15:49:06 +0100 [thread overview]
Message-ID: <31965.1176475746@redhat.com> (raw)
In-Reply-To: <20070413162909.c436a732.dada1@cosmosbay.com>
Eric Dumazet <dada1@cosmosbay.com> wrote:
> If space considerations are that important, we could then reserve one bit
> for the 'wait_lock spinlock'
That makes life quite a bit more tricky, though it does have the advantage
that it closes the reader-jumping-writer window I mentioned.
> Another possibility to save space would be to move wait_lock/wait_list
> outside of rw_semaphore, in a hashed global array.
I suspect moving wait_list out would be a bad idea. The ordering of things in
the list is very important. You need to perform several operations on the
list, all of which would be potentially slower:
(1) glance at the first element of the list to see what sort of wake up to do
(2) iteration of the list when waking up multiple readers
(3) seeing if the list is empty (so you know that there's no more contention)
Moving the spinlock out, on the other hand, might be worth it to cut down on
cacheline bouncing some more...
David
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-04-13 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 10:04 Nick Piggin
2007-04-13 10:25 ` Nick Piggin
2007-04-13 10:53 ` Andi Kleen
2007-04-13 11:20 ` Nick Piggin
2007-04-13 11:44 ` David Howells
2007-04-13 12:13 ` Christoph Hellwig
2007-04-13 12:09 ` David Howells
2007-04-13 12:43 ` Nick Piggin
2007-04-13 13:22 ` William Lee Irwin III
2007-04-13 13:31 ` David Howells
2007-04-13 14:03 ` Nick Piggin
2007-04-13 14:29 ` Eric Dumazet
2007-04-13 14:49 ` David Howells [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=31965.1176475746@redhat.com \
--to=dhowells@redhat.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.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