All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: mingo@elte.hu
Cc: green@namesys.com, zaitcev@redhat.com, mingo@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: cmpxchg in 2.5.38
Date: Wed, 25 Sep 2002 11:59:14 -0700 (PDT)	[thread overview]
Message-ID: <20020925.115914.106633211.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209251024580.4690-100000@localhost.localdomain>

   From: Ingo Molnar <mingo@elte.hu>
   Date: Wed, 25 Sep 2002 10:26:34 +0200 (CEST)
   
   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.

You can't define a crippled primitive like this Ingo.

What if someone else starts to use it?

And more importantly, if you can't use it on a datum shared between
userspace and the kernel, you have to name it something other than
cmpxchg or make the DRM use something else.

  parent reply	other threads:[~2002-09-25 19:04 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
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 [this message]
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=20020925.115914.106633211.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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.