From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: "Ion Badulescu" <ionut@badula.org>
Cc: "Jeff Garzik" <jgarzik@pobox.com>, <linux-kernel@vger.kernel.org>
Subject: Re: NETIF_F_SG question
Date: Mon, 3 Feb 2003 23:44:00 +0100 [thread overview]
Message-ID: <007201c2cbd5$bec836a0$020120b0@jockeXP> (raw)
In-Reply-To: Pine.LNX.4.44.0302031725090.27869-100000@guppy.limebrokerage.com
> On Mon, 3 Feb 2003, Joakim Tjernlund wrote:
>
> > > You get zerocopy, yes. :-) No HW cksum, no zerocopy.
> >
> > OK, but it should be easy to remove HW cksum as a condition to do zerocopy?
>
> Nope. You're looking at this the wrong way: the goal is not zero copy, but
> zero data access by CPU. Once you realize that, it's clear that SG alone
> is no good.
>
> This is not necessarily the only approach, but it is the current approach
> in the Linux IPv4 stack. It's not worth the effort to re-engineer the code
> in order to support the fast-disappearing hardware which supports SG but
> not cksums.
Agreed.
>
> > zerocopy without requiring HW cksums only OR could for instance the forwarding
> > procdure also benefit from SG without requiring HW cksums?
>
> The forwarding procedure is already dealing with linear buffers because
> 99.99% of the network cards on the market receive packets into one linear
> buffer. So again SG is useless for that.
I see, thanks for your patience with me.
Joakim
>
> Ion
prev parent reply other threads:[~2003-02-03 22:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 15:08 NETIF_F_SG question Joakim Tjernlund
2003-02-01 17:40 ` Jeff Garzik
2003-02-01 18:42 ` Joakim Tjernlund
2003-02-01 19:16 ` romieu
2003-02-01 22:16 ` Joakim Tjernlund
2003-02-02 1:39 ` Joakim Tjernlund
2003-02-03 21:18 ` Ion Badulescu
2003-02-03 22:22 ` Joakim Tjernlund
2003-02-03 22:34 ` Ion Badulescu
2003-02-03 22:44 ` Joakim Tjernlund [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='007201c2cbd5$bec836a0$020120b0@jockeXP' \
--to=joakim.tjernlund@lumentis.se \
--cc=ionut@badula.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.