From: "David S. Miller" <davem@redhat.com>
To: "Benjamin C.R. LaHaise" <blah@kvack.org>
Cc: michael@linuxmagic.com,
Jan Rekorajski <baggins@sith.mimuw.edu.pl>,
Chris Wedgwood <cw@f00f.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
waltje@uWalt.NL.Mugnet.ORG
Subject: Re: [UPDATE] zerocopy.. While working on ip.h stuff
Date: Mon, 26 Feb 2001 16:05:22 -0800 (PST) [thread overview]
Message-ID: <15002.61250.224811.987948@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1010226184514.9835E-100000@kanga.kvack.org>
In-Reply-To: <15002.58854.215318.882641@pizda.ninka.net> <Pine.LNX.3.96.1010226184514.9835E-100000@kanga.kvack.org>
Benjamin C.R. LaHaise writes:
> Since the ip header fits in the cache of some CPUs (like the P4),
> this becoming a cheaper operation than ever before.
At gigapacket rates, it becomes an issue. This guy is talking about
tinkering with new IP _options_, not just the header. So even if the
IP header itself fits totally in a cache line, the options afterwardsd
likely will not and thus require another cache miss.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-02-27 0:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 6:59 [UPDATE] zerocopy BETA 3 David S. Miller
2001-02-23 10:42 ` Jan Rekorajski
2001-02-25 3:38 ` Chris Wedgwood
2001-02-25 3:54 ` Jan Rekorajski
2001-02-26 23:25 ` [UPDATE] zerocopy.. While working on ip.h stuff David S. Miller
2001-02-26 23:47 ` Benjamin C.R. LaHaise
2001-02-27 0:05 ` David S. Miller [this message]
2001-02-27 0:11 ` Benjamin C.R. LaHaise
2001-02-27 3:41 ` Michael Peddemors
2001-02-27 3:24 ` Michael Peddemors
2001-02-26 23:46 ` Michael Peddemors
2001-02-26 23:23 ` Andi Kleen
2001-02-26 5:28 ` [UPDATE] zerocopy BETA 3 David S. Miller
[not found] <2137.983232656@ISI.EDU>
2001-02-27 1:53 ` [UPDATE] zerocopy.. While working on ip.h stuff Michael Peddemors
2001-02-27 2:31 ` Craig Milo Rogers
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=15002.61250.224811.987948@pizda.ninka.net \
--to=davem@redhat.com \
--cc=baggins@sith.mimuw.edu.pl \
--cc=blah@kvack.org \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@linuxmagic.com \
--cc=netdev@oss.sgi.com \
--cc=waltje@uWalt.NL.Mugnet.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).