All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Changli Gao <xiaosuo@gmail.com>
Cc: dhowells@redhat.com, Ingo Molnar <mingo@elte.hu>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Davide Libenzi <davidel@xmailserver.org>,
	Roland Dreier <rolandd@cisco.com>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <dada1@cosmosbay.com>,
	Christoph Lameter <cl@linux.com>,
	Andreas Herrmann <andreas.herrmann3@amd.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Takashi Iwai <tiwai@suse.de>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] sched: implement the exclusive wait queue as a LIFO queue
Date: Wed, 28 Apr 2010 16:00:06 +0100	[thread overview]
Message-ID: <14370.1272466806@redhat.com> (raw)
In-Reply-To: <v2x412e6f7f1004280753pd3438a3fv860edc580ecd6185@mail.gmail.com>

Changli Gao <xiaosuo@gmail.com> wrote:

> > How often do the two actually mix?  And if they do, is that really an
> > error?
> 
> The sock.sk_sleep is used by exclusive and non-exclusive wait queues.
> exclusive and non-exclusive is identified by wait queues, not wait
> queue heads. Maybe there is a historical reason. It is much like a
> hack.

But is it actually used in both modes at the same time?

David

  reply	other threads:[~2010-04-28 15:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28  5:03 [RFC] sched: implement the exclusive wait queue as a LIFO queue Changli Gao
2010-04-28  6:22 ` Changli Gao
2010-04-28  8:05   ` Changli Gao
2010-04-28  7:47 ` Xiaotian Feng
2010-04-28  7:47   ` Xiaotian Feng
2010-04-28  7:52   ` Changli Gao
2010-04-28  7:52     ` Changli Gao
2010-04-28  8:15     ` Yong Zhang
2010-04-28  8:15       ` Yong Zhang
2010-04-28  8:23       ` Changli Gao
2010-04-28  9:25         ` Johannes Weiner
2010-04-28  9:29         ` David Howells
2010-04-28 11:17           ` Changli Gao
2010-04-28 11:17             ` Changli Gao
2010-04-28 13:21             ` David Howells
2010-04-28 13:21             ` Jamie Lokier
2010-04-28 13:21               ` Jamie Lokier
2010-04-28 13:42               ` Changli Gao
2010-04-28 15:25                 ` Jamie Lokier
2010-04-28 15:49                   ` Changli Gao
2010-04-28 18:57             ` Davide Libenzi
2010-04-28  9:32 ` David Howells
2010-04-28 13:56   ` Changli Gao
2010-04-28 13:56     ` Changli Gao
2010-04-28 14:06     ` David Howells
2010-04-28 14:53       ` Changli Gao
2010-04-28 14:53         ` Changli Gao
2010-04-28 15:00         ` David Howells [this message]
2010-04-28 15:33           ` Changli Gao
2010-04-28 15:33             ` Changli Gao
2010-04-28  9:34 ` David Howells
2010-04-28 13:47   ` Changli Gao

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=14370.1272466806@redhat.com \
    --to=dhowells@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=andreas.herrmann3@amd.com \
    --cc=cl@linux.com \
    --cc=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --cc=davidel@xmailserver.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rolandd@cisco.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=tglx@linutronix.de \
    --cc=tiwai@suse.de \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xiaosuo@gmail.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.