linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Arjan van de Ven <arjanv@redhat.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH] 10/4  -ac to newer rmap
Date: Wed, 13 Nov 2002 19:33:48 +0000	[thread overview]
Message-ID: <20021113193348.A29582@infradead.org> (raw)
In-Reply-To: <20021113193041Z80262-23310+72@imladris.surriel.com>; from riel@conectiva.com.br on Wed, Nov 13, 2002 at 05:30:34PM -0200

>  /* 
>   * Wait for a page to get unlocked.
>   *
>   * This must be called with the caller "holding" the page,
>   * ie with increased "page->count" so that the page won't
>   * go away during the wait..
> - *
> - * The waiting strategy is to get on a waitqueue determined
> - * by hashing. Waiters will then collide, and the newly woken
> - * task must then determine whether it was woken for the page
> - * it really wanted, and go back to sleep on the waitqueue if
> - * that wasn't it. With the waitqueue semantics, it never leaves
> - * the waitqueue unless it calls, so the loop moves forward one
> - * iteration every time there is
> - * (1) a collision 
> - * and
> - * (2) one of the colliding pages is woken
> - *
> - * This is the thundering herd problem, but it is expected to
> - * be very rare due to the few pages that are actually being
> - * waited on at any given time and the quality of the hash function.
>   */

What is the pint of removing comments?

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

  reply	other threads:[~2002-11-13 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 19:30 Rik van Riel
2002-11-13 19:33 ` Christoph Hellwig [this message]
2002-11-13 19:37   ` Rik van Riel

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=20021113193348.A29582@infradead.org \
    --to=hch@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjanv@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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