linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Nick Piggin <npiggin@suse.de>
Subject: Re: [PATCH 1/2] scalable rw_mutex
Date: Sat, 12 May 2007 18:57:47 +0200	[thread overview]
Message-ID: <1178989068.19461.3.camel@lappy> (raw)
In-Reply-To: <20070512160428.GA173@tv-sign.ru>

On Sat, 2007-05-12 at 20:04 +0400, Oleg Nesterov wrote:
> On 05/12, Peter Zijlstra wrote:
> >
> > +static inline void rw_mutex_readers_dec(struct rw_mutex *rw_mutex)
> > +{
> > +	percpu_counter_dec(&rw_mutex->readers);
> > +	smp_wmb();
> > +}
> >
> > +void rw_mutex_read_unlock(struct rw_mutex *rw_mutex)
> > +{
> > +	rw_mutex_readers_dec(rw_mutex);
> > +	/*
> > +	 * on the slow path;
> > +	 * nudge the writer waiting for the last reader to go away
> > +	 */
> > +	if (unlikely(rw_mutex_reader_slow(rw_mutex)))
> > +		rw_mutex_writer_wake(rw_mutex);
> > +}
> >
> > +void rw_mutex_write_lock_nested(struct rw_mutex *rw_mutex, int subclass)
> > +{
> > +	mutex_lock_nested(&rw_mutex->write_mutex, subclass);
> > +
> > +	/*
> > +	 * block new readers
> > +	 */
> > +	mutex_lock_nested(&rw_mutex->read_mutex, subclass);
> > +	rw_mutex_status_set(rw_mutex, RW_MUTEX_READER_SLOW);
> > +	/*
> > +	 * and wait for all current readers to go away
> > +	 */
> > +	rw_mutex_writer_wait(rw_mutex, (rw_mutex_readers(rw_mutex) == 0));
> > +}
> 
> I think this is still not right, but when it comes to barriers we
> need a true expert (Paul cc-ed).
> 
> this code roughly does (the only reader does unlock)
> 
> 	READER			WRITER
> 
> 	readers = 0;		state = 1;
> 	wmb();			wmb();
> 	CHECK(state != 0)	CHECK(readers == 0)
> 
> We need to ensure that we can't miss both CHECKs. Either reader
> should see RW_MUTEX_READER_SLOW, o writer sees "readers == 0"
> and does not sleep.
> 
> In that case both barriers should be converted to smp_mb(). There
> was a _long_ discussion about STORE-MB-LOAD behaviour, and experts
> seem to believe everething is ok.

Ah, but note that both those CHECK()s have a rmb(), so that ends up
being:

	READER				WRITER

	readers = 0;			state = 1;
	wmb();				wmb();

	rmb();				rmb();		
	if (state != 0)			if (readers == 0)

and a wmb+rmb is a full mb, right?

> Another question. Isn't it possible to kill rw_mutex->status ?
> 
> I have a vague feeling you can change the code so that
> 
> 	rw_mutex_reader_slow() <=> "->waiter != NULL"
> 
> , but I am not sure.

If not now, it might be possible to make it so. Thanks for the
suggestion.

Peter

--
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>

  reply	other threads:[~2007-05-12 16:57 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11 13:15 [PATCH 0/2] convert mmap_sem to a " Peter Zijlstra
2007-05-11 13:15 ` [PATCH 1/2] " Peter Zijlstra
2007-05-11 14:03   ` Christoph Hellwig
2007-05-11 16:31   ` Andrew Morton
2007-05-11 17:07     ` Christoph Lameter
2007-05-11 18:05       ` Andrew Morton
2007-05-12 18:55         ` Andi Kleen
2007-05-12 18:06           ` Andrew Morton
2007-05-12 18:11             ` Andrew Morton
2007-05-16 23:28             ` Andrew Morton
2007-05-16 23:40               ` Christoph Lameter
2007-05-17  0:24                 ` Andrew Morton
2007-05-12 18:12           ` Oleg Nesterov
2007-05-12 19:21             ` Andi Kleen
2007-05-12 21:42               ` Oleg Nesterov
2007-05-11 17:57     ` Peter Zijlstra
2007-05-11 23:00   ` Oleg Nesterov
2007-05-12  7:39     ` Peter Zijlstra
2007-05-12 13:41     ` Peter Zijlstra
2007-05-12 16:04       ` Oleg Nesterov
2007-05-12 16:57         ` Peter Zijlstra [this message]
2007-05-12 18:03           ` Oleg Nesterov
2007-05-14 10:59             ` Peter Zijlstra
2007-05-14 11:36               ` Nick Piggin
2007-05-15  0:36               ` Paul E. McKenney
2007-05-15  7:43                 ` Peter Zijlstra
2007-05-15 15:29                   ` Paul E. McKenney
2007-05-15 16:17                     ` Peter Zijlstra
2007-05-15 18:52                       ` Paul E. McKenney
2007-05-11 13:15 ` [PATCH 2/2] mm: change mmap_sem over to the " Peter Zijlstra
2007-05-11 16:17   ` Andrew Morton
2007-05-11 17:12     ` Peter Zijlstra
2007-05-11 18:08       ` Andrew Morton
2007-05-14 11:54         ` Nick Piggin
2007-05-11 15:56 ` [PATCH 0/2] convert mmap_sem to a " Ingo Molnar
2007-05-11 16:52   ` Eric Dumazet
2007-05-11 17:18     ` Peter Zijlstra
2007-05-14 12:07       ` Nick Piggin
2007-05-14 12:57         ` Peter Zijlstra
2007-05-11 17:08   ` Christoph Lameter
2007-05-14 11:58   ` Nick Piggin
2007-05-14 12:38     ` Peter Zijlstra
2007-05-12  9:27 ` Esben Nielsen
2007-05-12 10:01   ` Peter Zijlstra
2007-05-12 13:44     ` Esben Nielsen
2007-05-12 14:33       ` Ingo Molnar
2007-05-12 15:34         ` Esben Nielsen
2007-05-12 15:42           ` Ingo Molnar
2007-05-12 15:26       ` Eric Dumazet
2007-05-14  8:50         ` Esben Nielsen

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=1178989068.19461.3.camel@lappy \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=oleg@tv-sign.ru \
    --cc=tglx@linutronix.de \
    /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