From: Andi Kleen <andi@firstfloor.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
jgarzik@pobox.com, netdev@vger.kernel.org
Subject: Re: [RFC] netdevice ops
Date: 19 May 2007 16:18:02 +0200 [thread overview]
Message-ID: <p737ir4ew2t.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070517225833.1b7e6acf@localhost>
Stephen Hemminger <shemminger@linux-foundation.org> writes:
>
> I would think a non-conditional deref would be easily pipelined.
> If the net_device struct was more cache dense, it probably would
> even out.
It might be a good idea to consider strategic prefetch points for it.
e.g. TCP executes quite a lot of code until it finally decides to dev_queue_xmit.
Prefetching before that might be a good idea.
-Andi
prev parent reply other threads:[~2007-05-19 13:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 4:07 [RFC] netdevice ops Stephen Hemminger
2007-05-18 4:23 ` Ben Greear
2007-05-18 4:49 ` David Miller
2007-05-18 6:42 ` Ben Greear
2007-05-18 4:50 ` David Miller
2007-05-18 4:54 ` Jeff Garzik
2007-05-18 5:05 ` David Miller
2007-05-18 5:58 ` Stephen Hemminger
2007-05-19 14:18 ` Andi Kleen [this message]
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=p737ir4ew2t.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).