From: "David S. Miller" <davem@redhat.com>
To: akpm@digeo.com
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [RFC][PATCH] net drivers and cache alignment
Date: Sun, 08 Dec 2002 12:00:44 -0800 (PST) [thread overview]
Message-ID: <20021208.120044.08024570.davem@redhat.com> (raw)
In-Reply-To: <3DF28748.186AB31F@digeo.com>
From: Andrew Morton <akpm@digeo.com>
Date: Sat, 07 Dec 2002 15:42:00 -0800
"David S. Miller" wrote:
> non-smp machines lack L2 caches? That's new to me :-)
>
> More seriously, there are real benefits on non-SMP systems.
Then I am most confused. None of these fields will be put under
busmastering or anything like that, so what advantage is there in
spreading them out?
When you are in the "tx path" you'll take one L2 cache miss
to bring all the necessary information into the cpu's caches.
Otherwise, when data is arbitrarily scattered over multiple L2
cache lines, you'll need to service potentially more L2 cache
misses.
This optimization has nothing to do with false data sharing amoungst
multiple processors. It's about packing the data accesses optimally
for specific code paths.
next prev parent reply other threads:[~2002-12-08 20:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 22:37 [RFC][PATCH] net drivers and cache alignment Jeff Garzik
2002-12-07 22:40 ` David S. Miller
2002-12-07 22:46 ` Jeff Garzik
2002-12-07 23:06 ` Jeff Garzik
2002-12-07 23:29 ` Andrew Morton
2002-12-07 23:30 ` David S. Miller
2002-12-07 23:42 ` Andrew Morton
2002-12-07 23:51 ` Andrew Morton
2002-12-15 18:31 ` Jes Sorensen
2002-12-08 20:00 ` David S. Miller [this message]
2002-12-07 23:36 ` Jeff Garzik
2002-12-07 23:37 ` J.A. Magallon
2002-12-07 23:42 ` Jeff Garzik
2002-12-07 23:45 ` Andrew Morton
2002-12-07 23:52 ` J.A. Magallon
2002-12-08 1:14 ` Daniel Jacobowitz
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=20021208.120044.08024570.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@digeo.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).