mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Adam J. Richter" <adam@yggdrasil.com>, <dhowells@redhat.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Patch: linux-2.5.29 __downgrade_write() for CONFIG_RWSEM_GENERIC_SPINLOCK
Date: Mon, 29 Jul 2002 00:55:26 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0207290048070.8911-100000@serv> (raw)
In-Reply-To: <20020728190851.A14392@infradead.org>

Hi,

On Sun, 28 Jul 2002, Christoph Hellwig wrote:

> -static inline struct rw_semaphore *__rwsem_do_wake(struct rw_semaphore *sem)
> +static inline struct rw_semaphore *__rwsem_do_wake(struct rw_semaphore *sem, int wakewrite)
>  {
>  	struct rwsem_waiter *waiter;
>  	int woken;
> @@ -56,7 +57,14 @@ static inline struct rw_semaphore *__rws
>
>  	waiter = list_entry(sem->wait_list.next,struct rwsem_waiter,list);
>
> -	/* try to grant a single write lock if there's a writer at the front of the queue
> +	if (!wakewrite) {
> +		if (waiter->flags & RWSEM_WAITING_FOR_WRITE)
> +			goto out;
> +		goto dont_wake_writers;
> +	}
> +
> +	/* if we are allowed to wake writers try to grant a single write lock if there's a
> +	 * writer at the front of the queue
>  	 * - we leave the 'waiting count' incremented to signify potential contention
>  	 */
>  	if (waiter->flags & RWSEM_WAITING_FOR_WRITE) {

You don't really need that extra argument, testing sem->activity should do
the same job.
If you exchange the wakewrite (or sem->activity) test and the
waiter->flags you can fold it into the next test (this means all the extra
work would only be done, if we have a writer waiting at the top).

bye, Roman


  reply	other threads:[~2002-07-28 22:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-28 17:50 Adam J. Richter
2002-07-28 18:07 ` Roman Zippel
2002-07-28 18:08 ` Christoph Hellwig
2002-07-28 22:55   ` Roman Zippel [this message]
2002-07-29  7:42     ` David Howells
2002-07-29  8:01       ` Roman Zippel
2002-07-29  8:31         ` David Howells
2002-07-29  9:13           ` David Howells
2002-07-29 11:42             ` Roman Zippel
2002-07-29 12:08               ` David Howells
2002-07-29 12:46                 ` Roman Zippel

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=Pine.LNX.4.44.0207290048070.8911-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=adam@yggdrasil.com \
    --cc=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --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®