linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Oleg Drokin <green@namesys.com>
Cc: "David S. Miller" <davem@redhat.com>, <zaitcev@redhat.com>,
	<mingo@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: cmpxchg in 2.5.38
Date: Wed, 25 Sep 2002 10:26:34 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209251024580.4690-100000@localhost.localdomain> (raw)
In-Reply-To: <20020925120725.A23559@namesys.com>


On Wed, 25 Sep 2002, Oleg Drokin wrote:

> Ingo's argument was that since there is only one place in code that
> accesses that variable (map->page), it is safe to rely on such a
> crippled cmpxchg implementation.

yes. It's only this place in the code that ever modifies that word, and
that happens only once during the lifetime of this address, so i'll rather
add a spinlock to the generic PID allocator code, it's a very very rare
slowpath.

	Ingo


  reply	other threads:[~2002-09-25  8:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25  5:00 cmpxchg in 2.5.38 Pete Zaitcev
2002-09-25  4:54 ` David S. Miller
2002-09-25  7:18 ` Oleg Drokin
2002-09-25  7:47   ` David S. Miller
2002-09-25  8:07     ` Oleg Drokin
2002-09-25  8:26       ` Ingo Molnar [this message]
2002-09-25  8:48         ` [patch] pidhash-2.5.38-A0 Ingo Molnar
2002-09-25 12:04         ` cmpxchg in 2.5.38 Geert Uytterhoeven
2002-09-25 17:42         ` Pete Zaitcev
2002-09-25 19:34           ` Ingo Molnar
2002-09-25 20:03             ` David S. Miller
2002-09-25 18:59         ` David S. Miller
2002-09-25 19:02         ` David S. Miller

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.0209251024580.4690-100000@localhost.localdomain \
    --to=mingo@elte.hu \
    --cc=davem@redhat.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=zaitcev@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).