From: David Mosberger <davidm@hpl.hp.com>
To: "David S. Miller" <davem@redhat.com>
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 19:18:38 -0800 [thread overview]
Message-ID: <15464.35214.669412.477377@napali.hpl.hp.com> (raw)
In-Reply-To: <20020211.190449.55725714.davem@redhat.com>
In-Reply-To: <15464.33256.837784.657759@napali.hpl.hp.com> <20020211.185100.68039940.davem@redhat.com> <15464.34183.282646.869983@napali.hpl.hp.com> <20020211.190449.55725714.davem@redhat.com>
>>>>> On Mon, 11 Feb 2002 19:04:49 -0800 (PST), "David S. Miller" <davem@redhat.com> said:
DaveM> You don't have any facts, you just "think" it will slow
DaveM> things down because of the pointer dereference. I challenge
DaveM> you to show it actually shows up on the performance radar.
DaveM> The thing is going to be fully hot in the cache all the time,
DaveM> there is no way you'll take a cache miss for this
DaveM> dereference.
Let's see: on Itanium, a ld takes up an M slot and has a 2 cycle
access latency (if in the first level cache). This may or may not be
noticable in benchmarks, but it certainly won't go faster. And all
this just for task coloring (which we can do with the old set up just
fine)?
--david
next prev parent reply other threads:[~2002-02-12 3:19 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 [this message]
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
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=15464.35214.669412.477377@napali.hpl.hp.com \
--to=davidm@hpl.hp.com \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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®