From: William Lee Irwin III <wli@holomorphy.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Gianni Tedesco <gianni@scaramanga.co.uk>,
Linux Kernel Mailing List <Linux-Kernel@Vger.Kernel.ORG>,
Linus Torvalds <Torvalds@Transmeta.COM>,
Andrew Morton <AKPM@Digeo.COM>
Subject: Re: const from include/asm-i386/byteorder.h
Date: Mon, 2 Jun 2003 05:40:16 -0700 [thread overview]
Message-ID: <20030602124016.GP8978@holomorphy.com> (raw)
In-Reply-To: <16091.17602.257293.364468@laputa.namesys.com>
William Lee Irwin III writes:
>> Someone needs to doublecheck whether this actually works. Last I heard,
On Mon, Jun 02, 2003 at 04:36:18PM +0400, Nikita Danilov wrote:
> I don't quite understand. __attribute_const is defined as
> #define __attribute_const __attribute__ ((__const__))
> so, after preprocessing prototypes of get_current() and
> current_thread_info() will be the same as before patch, modulo spacing.
William Lee Irwin III writes:
>> it did not, but that could have changed since. It vaguely appears some
>> assumption about it working was made recently since __const__ was there.
On Mon, Jun 02, 2003 at 04:36:18PM +0400, Nikita Danilov wrote:
> I am currently running ./fsstress -p 111 on patched kernel on 2*XEON
> 2.20GHz with hyper threading.
Sounds good. If you could doublecheck the assembly to make sure it's
doing the right thing, that would be good, too.
Thanks.
-- wli
next prev parent reply other threads:[~2003-06-02 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 14:10 const from include/asm-i386/byteorder.h Nikita Danilov
2003-05-31 18:49 ` Gianni Tedesco
2003-05-31 18:57 ` William Lee Irwin III
2003-06-02 11:51 ` Nikita Danilov
2003-06-02 12:14 ` William Lee Irwin III
2003-06-02 12:36 ` Nikita Danilov
2003-06-02 12:40 ` William Lee Irwin III [this message]
2003-06-02 12:59 ` Nikita Danilov
2003-06-02 13:08 ` William Lee Irwin III
2003-06-02 13:21 ` Gianni Tedesco
2003-06-02 13:37 ` Adrian Bunk
2003-06-02 14:46 ` Nikita Danilov
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=20030602124016.GP8978@holomorphy.com \
--to=wli@holomorphy.com \
--cc=AKPM@Digeo.COM \
--cc=Linux-Kernel@Vger.Kernel.ORG \
--cc=Nikita@Namesys.COM \
--cc=Torvalds@Transmeta.COM \
--cc=gianni@scaramanga.co.uk \
/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