From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Herbert Xu <herbert.xu@redhat.com>
Cc: Chris Snook <csnook@redhat.com>, Andi Kleen <ak@suse.de>,
sebastian@breakpoint.cc, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/2] i386: use asm() like the other atomic operations already do.
Date: Thu, 16 Aug 2007 11:37:52 +1000 [thread overview]
Message-ID: <46C3AA70.9010000@yahoo.com.au> (raw)
In-Reply-To: <20070815234434.GC28775@gondor.apana.org.au>
Herbert Xu wrote:
> On Wed, Aug 15, 2007 at 01:02:23PM -0400, Chris Snook wrote:
>
>>Herbert Xu wrote:
>>>I'm still unconvinced why we need this because nobody has
>>>brought up any examples of kernel code that legitimately
>>>need this.
>>
>>There's plenty of kernel code that *wants* this though. If we can
>
>
> You keep saying this yet everytime I ask for an example I
> get nothing.
Agreed. Simplest thing to do will be to post those patches which
eliminate the register-clobbering barriers, shrink binaries, etc.
for all that code that wants this.
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2007-08-16 1:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 22:38 [patch 0/2] use asm() for atomic_{read|set} Sebastian Siewior
2007-08-14 22:38 ` [patch 1/2] i386: use asm() like the other atomic operations already do Sebastian Siewior
2007-08-15 0:20 ` Andi Kleen
2007-08-15 7:04 ` Sebastian Siewior
2007-08-15 8:40 ` Herbert Xu
2007-08-15 13:02 ` Satyam Sharma
2007-08-15 13:45 ` Sebastian Siewior
2007-08-15 17:02 ` Chris Snook
2007-08-15 23:44 ` Herbert Xu
2007-08-16 1:37 ` Nick Piggin [this message]
2007-08-16 19:23 ` Chris Snook
2007-08-17 0:04 ` Herbert Xu
2007-08-14 22:38 ` [patch 2/2] x86_64: " Sebastian Siewior
-- strict thread matches above, loose matches on Subject: below --
2007-08-15 20:54 [patch 0/2] use asm() for atomic_{read|set} (shot 2) Sebastian Siewior
2007-08-15 20:54 ` [patch 1/2] i386: use asm() like the other atomic operations already do Sebastian Siewior
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=46C3AA70.9010000@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=ak@suse.de \
--cc=csnook@redhat.com \
--cc=herbert.xu@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian@breakpoint.cc \
/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