From: Manfred Spraul <manfred@colorfullife.com>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: Alan <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.5] smp_call_function_mask
Date: Tue, 21 Jan 2003 18:13:22 +0100 [thread overview]
Message-ID: <3E2D7FB2.80806@colorfullife.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301210318540.2653-100000@montezuma.mastecende.com>
Zwane Mwaikambo wrote:
>On Tue, 21 Jan 2003, Zwane Mwaikambo wrote:
>
>
>
>>On Tue, 21 Jan 2003, Manfred Spraul wrote:
>>
>>
>>
>>>from 2.5.52, <asm-i386/atomic.h>
>>> #define atomic_read(v) ((v)->counter)
>>>AFAIK atomic_read never contained locked bus cycles.
>>>
>>>Btw, Zwane, what about removing non_atomic from the prototype?
>>>
>>>
>>The funny thing is, there are about 3 different versions of
>>smp_call_function and removing nonatomic would reduce the argument count
>>
>>
You can blame me for the mess with smp_call_function:
2.2 supported nonatomic calls. I have no idea if that was deadlock free.
But noone used the 'retry/nonatomic' parameter, noone handled an error
return of smp_call_function (some callers panic).
Thus I've removed these features from i386, without changing the
prototype. I think all archs have picked that up now.
But retry/nonatomic should not spread into new functions.
--
Manfred
next prev parent reply other threads:[~2003-01-21 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 7:13 [PATCH][2.5] smp_call_function_mask Manfred Spraul
2003-01-21 8:07 ` Zwane Mwaikambo
2003-01-21 9:21 ` Zwane Mwaikambo
2003-01-21 17:13 ` Manfred Spraul [this message]
2003-01-21 17:49 ` Zwane Mwaikambo
2003-01-21 23:14 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 5:18 Zwane Mwaikambo
2003-01-17 5:44 ` Andrew Morton
2003-01-17 5:56 ` Zwane Mwaikambo
2003-01-20 23:19 ` Alan
2003-01-21 7:16 ` Zwane Mwaikambo
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=3E2D7FB2.80806@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@holomorphy.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