From: "David S. Miller" <davem@redhat.com>
To: rth@twiddle.net
Cc: davidm@hpl.hp.com, anton@samba.org, linux-kernel@vger.kernel.org,
zippel@linux-m68k.org
Subject: Re: thread_info implementation
Date: Mon, 11 Feb 2002 21:32:48 -0800 (PST) [thread overview]
Message-ID: <20020211.213248.48398226.davem@redhat.com> (raw)
In-Reply-To: <20020211212644.A20387@twiddle.net>
In-Reply-To: <20020211.192334.123921982.davem@redhat.com> <15464.36074.246502.582895@napali.hpl.hp.com> <20020211212644.A20387@twiddle.net>
From: Richard Henderson <rth@twiddle.net>
Date: Mon, 11 Feb 2002 21:26:44 -0800
On another topic, I'm considering having $8 continue to be current
and using the two-insn stack mask to get current_thread_info and
measuring the size difference that makes.
I might put 'current' into %g7 on sparc but currently I don't think
it's worth it myself.
BTW, your "4 issue" comments assume the cpu can do 4 non-FPU
instructions per cycle, most I am aware of cannot and I think ia64
even falls into the "cannot" category. Doesn't it?
next prev parent reply other threads:[~2002-02-12 5:34 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 21:08 Roman Zippel
2002-02-11 20:50 ` Anton Blanchard
2002-02-12 0:01 ` Roman Zippel
2002-02-12 0:10 ` David Howells
2002-02-12 0:22 ` Roman Zippel
2002-02-12 0:46 ` David S. Miller
2002-02-12 0:57 ` Roman Zippel
2002-02-12 0:57 ` David S. Miller
2002-02-12 1:10 ` Roman Zippel
2002-02-12 13:01 ` Bjorn Wesen
2002-02-12 13:49 ` David S. Miller
2002-02-12 1:01 ` David Mosberger
2002-02-12 1:21 ` David Mosberger
2002-02-12 1:36 ` David Mosberger
2002-02-12 1:53 ` David Mosberger
2002-02-12 2:30 ` David Mosberger
2002-02-12 2:46 ` David Mosberger
2002-02-12 3:01 ` David Mosberger
2002-02-12 3:18 ` David Mosberger
2002-02-12 3:32 ` David Mosberger
2002-02-12 4:16 ` David Mosberger
2002-02-12 4:33 ` David Mosberger
2002-02-12 5:26 ` Richard Henderson
2002-02-12 5:50 ` David Mosberger
2002-02-13 11:18 ` Anton Blanchard
2002-02-12 5:32 ` David S. Miller [this message]
2002-02-12 5:57 ` Richard Henderson
2002-02-12 2:49 ` Davide Libenzi
2002-02-12 1:07 ` David S. Miller
2002-02-12 1:32 ` David S. Miller
2002-02-12 1:41 ` David S. Miller
2002-02-12 2:22 ` David S. Miller
2002-02-12 2:36 ` David S. Miller
2002-02-12 2:51 ` David S. Miller
2002-02-12 3:04 ` David S. Miller
2002-02-12 3:23 ` David S. Miller
2002-02-12 3:42 ` David S. Miller
2002-02-12 4:21 ` David S. Miller
2002-02-12 17:14 ` Pavel Machek
2002-02-13 0:46 ` David S. Miller
2002-02-13 1:30 ` Roman Zippel
2002-02-12 9:12 ` Roman Zippel
2002-02-12 9:30 ` Jeff Garzik
2002-02-12 10:14 ` Roman Zippel
2002-02-12 13:21 ` David Howells
2002-02-12 19:15 ` David Mosberger
2002-02-12 19:38 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2002-02-11 17:39 Arkadiy Chapkis - Arc
2002-02-11 20:19 ` Robert Love
2002-02-11 20:42 ` Luigi Genoni
2002-02-11 20:48 ` Robert Love
2002-02-11 23:37 ` Jeff Garzik
2002-02-11 23:49 ` Richard Henderson
2002-02-12 0:09 ` Dave Jones
2002-02-12 0:20 ` Jeff Garzik
2002-02-12 0:24 ` Dave Jones
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=20020211.213248.48398226.davem@redhat.com \
--to=davem@redhat.com \
--cc=anton@samba.org \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®