public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC,PATCH] use nonatomic bitops for cpumask_t
Date: Sat, 29 May 2004 11:46:45 +0200	[thread overview]
Message-ID: <40B85C05.5080302@colorfullife.com> (raw)
In-Reply-To: <40B85071.8090402@colorfullife.com>

Manfred Spraul wrote:

> Hi,
>
> I'm checking for callers that rely on the atomicity of the bitops, but 
> so far everyone has it's own locks.

One exception is the x86 tlb flush code, thus my patch is wrong. We 
could add nonatomic __cpu_set and __cpu_clear bitops, but I'm not sure 
if it's worth the effort, cpu bitops aren't that common 
(kernel/rcupdate.c and balance_node could use the __ versions).

Sorry for the noise (and don't check who wrote the x86 tlb flush code)
--
    Manfred


  reply	other threads:[~2004-05-29  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-29  8:57 [RFC,PATCH] use nonatomic bitops for cpumask_t Manfred Spraul
2004-05-29  9:46 ` Manfred Spraul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-29 11:02 Mikael Pettersson

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=40B85C05.5080302@colorfullife.com \
    --to=manfred@colorfullife.com \
    --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