From: Avi Kivity <avi@argo.co.il>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andreas Hartmann <andihartmann@01019freenet.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: More performance for the TCP stack by using additional hardware chip on NIC
Date: Sun, 17 Apr 2005 15:32:53 +0300 [thread overview]
Message-ID: <1113741172.15803.55.camel@avik.scalemp> (raw)
In-Reply-To: <1113735452.17394.33.camel@laptopd505.fenrus.org>
On Sun, 2005-04-17 at 13:57, Arjan van de Ven wrote:
> >
> > TOEs can remove the data copy on receive. In some applications (notably
> > storage), where the application does not touch most of the data, this is
> > a significant advantage that cannot be achieved in a software-only
> > solution.
>
> other solutions can too. Search the archives for posts from Dave Miller
> and Jeff Garzik on these issues. Note that TOEs per se don't do this,
> specific treats of interfaces to TOE *may* allow this. The interesting
> part is that the parts of the interface that would allow this can be
> implemented without TOE (and all the downsides of full TOE such as
> bypassing firewall rules etc etc) just as well.
>
I see. if you are referring to Willy's trick in the other post, then I
agree. it has still more overhead than full offload, so only
measurements can tell if it is enough (and, of course, need to wait for
the hardware to materialize).
> > a copyless solution is probably necessary to achieve 10Gb/s speeds.
>
> I've heard the same say abot 100Mbit and 1Gbit. And neither has been
> proven true. Don't get me wrong, avoiding copies is always nice, and on
> sending linux already enables that (depending on the applications
> capabilities). But I personally find it hard to accept that full
> copyless operation is a strict requirement to achieve 10Gb/s.
>
> What sure will be required to achieve efficient 10Gb/s performance is a
> whole lot of tuning in the network stack and potentially even in the
> tcp/ip layer to allow for bigger buffers etc. But I'm pretty sure that
> effort is underway already or will be soon...
>
amen.
Avi
next prev parent reply other threads:[~2005-04-17 12:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 8:17 Andreas Hartmann
2005-04-17 9:07 ` Arjan van de Ven
2005-04-17 10:29 ` Avi Kivity
2005-04-17 10:57 ` Arjan van de Ven
2005-04-17 12:32 ` Avi Kivity [this message]
2005-04-17 11:30 ` Willy Tarreau
2005-04-17 12:15 ` Avi Kivity
2005-04-17 19:43 ` Bernd Eckenfels
2005-04-17 20:36 ` David S. Miller
2005-04-18 5:35 ` Avi Kivity
2005-04-17 23:37 ` Horst von Brand
2005-04-18 4:08 ` Kyle Moffett
2005-04-18 4:28 ` Willy Tarreau
[not found] <3Udkm-7rV-7@gated-at.bofh.it>
[not found] ` <3Ue6L-867-19@gated-at.bofh.it>
[not found] ` <3Ufm9-IB-3@gated-at.bofh.it>
[not found] ` <3Ugid-1w6-25@gated-at.bofh.it>
2005-04-17 19:04 ` Andreas Hartmann
2005-04-18 8:27 ` Denis Vlasenko
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=1113741172.15803.55.camel@avik.scalemp \
--to=avi@argo.co.il \
--cc=andihartmann@01019freenet.de \
--cc=arjan@infradead.org \
--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 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®