From: Michel Lespinasse <walken@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Waychison <mikew@google.com>,
Suleiman Souhlal <suleiman@google.com>,
Ying Han <yinghan@google.com>
Subject: Re: [PATCH 07/10] generic rwsem: implement down_read_critical() / up_read_critical()
Date: Mon, 17 May 2010 16:13:31 -0700 [thread overview]
Message-ID: <20100517231331.GA30847@google.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1005171532430.4195@i5.linux-foundation.org>
On Mon, May 17, 2010 at 03:44:24PM -0700, Linus Torvalds wrote:
> You didn't update the comment for the new name here...
>
> > - when the rwsem is write owned, down_read_unfair() callers get queued in
> > front of threads trying to acquire the rwsem by other means.
>
> .. or here. In this case, it really is more about "unfairness", but I'm
> not convinced it should be so in the naming anyway, even if internally it
> might be __down_read_unfair. "critical" I think covers both.
Gah! Sorry for missing the comment updates. I agree with you on the naming,
I just didn't remember about the comment.
Will send identical patch with the correct comment as reply to this.
> Anyway, the series looks mostly acceptable to me in this form. I think it
> conceptually works out, and I think that the non-preemption guarantee
> should mean that starvation of writers is not likely an issue. However,
> I'd definitely like some second opinions on it. I'm not going to apply
> this series without acks from people. So you should try to convince DavidH
> too that this actually really does matter and makes sense.
I'll see what I can do here. Thanks !
--
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
next prev parent reply other threads:[~2010-05-17 23:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 22:25 [PATCH 00/10] V3: rwsem changes + down_read_critical() proposal Michel Lespinasse
2010-05-17 22:25 ` [PATCH 01/10] x86 rwsem: minor cleanups Michel Lespinasse
2010-05-19 11:47 ` David Howells
2010-05-20 21:37 ` Michel Lespinasse
2010-05-17 22:25 ` [PATCH 02/10] rwsem: fully separate code pathes to wake writers vs readers Michel Lespinasse
2010-05-19 12:04 ` David Howells
2010-05-20 21:48 ` Michel Lespinasse
2010-05-17 22:25 ` [PATCH 03/10] rwsem: lighter active count checks when waking up readers Michel Lespinasse
2010-05-19 12:25 ` David Howells
2010-05-20 22:33 ` Michel Lespinasse
2010-05-21 8:06 ` David Howells
2010-05-17 22:25 ` [PATCH 04/10] rwsem: let RWSEM_WAITING_BIAS represent any number of waiting threads Michel Lespinasse
2010-05-19 12:33 ` David Howells
2010-05-17 22:25 ` [PATCH 05/10] rwsem: wake queued readers when writer blocks on active read lock Michel Lespinasse
2010-05-19 12:44 ` David Howells
2010-05-17 22:25 ` [PATCH 06/10] rwsem: smaller wrappers around rwsem_down_failed_common Michel Lespinasse
2010-05-19 12:51 ` David Howells
2010-05-17 22:25 ` [PATCH 07/10] generic rwsem: implement down_read_critical() / up_read_critical() Michel Lespinasse
2010-05-17 22:44 ` Linus Torvalds
2010-05-17 23:13 ` Michel Lespinasse [this message]
2010-05-17 23:20 ` Michel Lespinasse
2010-05-19 13:21 ` David Howells
2010-05-19 23:47 ` Michel Lespinasse
2010-05-21 3:35 ` Michel Lespinasse
2010-05-17 22:25 ` [PATCH 08/10] rwsem: down_read_critical infrastructure support Michel Lespinasse
2010-05-19 13:34 ` David Howells
2010-05-20 23:30 ` Michel Lespinasse
2010-05-21 8:03 ` David Howells
2010-05-17 22:25 ` [PATCH 09/10] x86 rwsem: down_read_critical implementation Michel Lespinasse
2010-05-19 14:36 ` David Howells
2010-05-17 22:25 ` [PATCH 10/10] Use down_read_critical() for /sys/<pid>/exe and /sys/<pid>/maps files Michel Lespinasse
2010-05-19 15:21 ` David Howells
2010-05-21 2:44 ` Michel Lespinasse
2010-05-22 1:49 ` Michel Lespinasse
2010-05-25 9:42 ` David Howells
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=20100517231331.GA30847@google.com \
--to=walken@google.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=mingo@elte.hu \
--cc=suleiman@google.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghan@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.