From: jamal <hadi@cyberus.ca>
To: Rick Jones <raj@cup.hp.com>
Cc: Ion Badulescu <ionut@cs.columbia.edu>,
Andrew Morton <andrewm@uow.edu.au>,
lkml <linux-kernel@vger.kernel.org>,
"netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: Re: Still not sexy! (Re: sendfile+zerocopy: fairly sexy (nothing todowith ECN)
Date: Sun, 4 Feb 2001 14:48:34 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.30.0102041426180.15417-100000@shell.cyberus.ca> (raw)
In-Reply-To: <3A77777D.E1A998FC@cup.hp.com>
On Tue, 30 Jan 2001, Rick Jones wrote:
> > > How does ZC/SG change the nature of the packets presented to the NIC?
> >
> > what do you mean? I am _sure_ you know how SG/ZC work. So i am suspecting
> > more than socratic view on life here. Could be influence from Aristotle;->
>
> Well, I don't know the specifics of Linux, but I gather from what I've
> read on the list thusfar, that prior to implementing SG support, Linux
> NIC drivers would copy packets into single contiguous buffers that were
> then sent to the NIC yes?
>
yes.
> If so, the implication is with SG going, that copy no longer takes
> place, and so a chain of buffers is given to the NIC.
>
yes.
> Also, if one is fully ZC :) pesky things like protocol headers can
> naturally end-up in separate buffers.
>
yes.
> So, now you have to ask how well any given NIC follows chains of
> buffers. At what number of buffers is the overhead in the NIC of
> following the chains enough to keep it from achieving link-rate?
>
hmmm... not sure how you would enforce this today or why you would
want that. Alexey, Dave?
The kernel should be able to break it into two buffers(with netperf,
for example -- header + data).
Ok, probably with tux-http 3 (header, data, trailler).
> One way to try and deduce that would be to meld some of the SG and preSG
> behaviours and copy packets into varying numbers of buffers per packet
> and measure the resulting impact on throughput through the NIC.
>
If only time were on my hands i'd love to do this. Alas.
NOTE also, that effect would also be an effect of the specif NIC.
> rick jones
>
> As time marches on, the orders of magnitude of the constants may change,
> but basic concepts still remain, and the "lessons" learned in the past
> by one generation tend to get relearned in the next :) for example -
> there is no such a thing as a free lunch... :)
;->
BTW, i am reading one of your papers (circa 1993 ;->, "we go fast with a
little help from your apps") in which you make an interesting
observation. That (figure 2) there is "a considerable increase in
efficiency but not a considerable increase in throughput" .... I "scanned"
to the end of the paper and dont see an explanation.
I've made a somehow similar observation with the current zc patches and
infact observed that throughput goes down with the linux zc patches.
[This is being contested but no-one else is testing at gigE, so my word is
the only truth].
Of course your paper doesnt talk about sendfile rather the page pinning +
COW tricks (which are considered taboo in Linux) but i do sense a
relationship.
cheers,
jamal
PS:- I dont have "my" machines yet and i have a feeling it will be a while
before i re-run the tests; however, i have created a patch for
linux-sendfile with netperf. Please take a look at it at:
http://www.cyberus.ca/~hadi/patch-nperf-sfile-linux.gz
tell me if is missing anything and if it is ok, could you please merge in
your tree?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-04 19:56 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 5:45 sendfile+zerocopy: fairly sexy (nothing to do with ECN) Andrew Morton
2001-01-27 6:20 ` Aaron Lehmann
2001-01-27 8:19 ` Andrew Morton
2001-01-27 10:09 ` Ion Badulescu
2001-01-27 10:45 ` Andrew Morton
2001-01-30 6:00 ` David S. Miller
2001-01-30 12:44 ` Andrew Morton
2001-01-30 12:52 ` David S. Miller
2001-01-30 14:58 ` Andrew Morton
2001-01-30 17:49 ` Chris Wedgwood
2001-01-30 22:17 ` David S. Miller
2001-01-31 0:31 ` Chris Wedgwood
2001-01-31 0:45 ` David S. Miller
2001-01-30 22:28 ` David S. Miller
2001-01-30 23:34 ` Andrew Morton
2001-02-02 10:12 ` Andrew Morton
2001-02-02 12:14 ` Trond Myklebust
2001-02-02 17:51 ` David Lang
2001-02-02 22:46 ` David S. Miller
2001-02-02 22:57 ` David Lang
2001-02-03 2:27 ` James Sutherland
2001-02-02 23:09 ` David S. Miller
2001-02-02 23:13 ` David Lang
2001-02-02 23:28 ` Jeff Barrow
2001-02-02 23:31 ` David S. Miller
2001-01-27 10:05 ` Ion Badulescu
2001-01-27 10:39 ` Andrew Morton
2001-01-27 12:49 ` jamal
2001-01-30 1:06 ` Ion Badulescu
2001-01-30 2:48 ` jamal
2001-01-30 3:26 ` Ion Badulescu
2001-01-31 0:53 ` Still not sexy! (Re: " jamal
2001-01-31 0:59 ` Ingo Molnar
2001-01-31 1:04 ` jamal
2001-01-31 1:14 ` Ingo Molnar
2001-01-31 1:39 ` jamal
2001-01-31 11:21 ` Malcolm Beattie
2001-01-31 11:24 ` Ingo Molnar
2001-01-31 1:10 ` Still not sexy! (Re: sendfile+zerocopy: fairly sexy (nothing to dowith ECN) Rick Jones
2001-01-31 1:45 ` jamal
2001-01-31 2:25 ` Still not sexy! (Re: sendfile+zerocopy: fairly sexy (nothing todowith ECN) Rick Jones
2001-02-04 19:48 ` jamal [this message]
2001-02-05 18:51 ` Rick Jones
2001-02-05 5:13 ` David S. Miller
2001-01-27 12:43 ` sendfile+zerocopy: fairly sexy (nothing to do with ECN) jamal
2001-01-27 13:29 ` Andrew Morton
2001-01-27 14:15 ` jamal
2001-01-28 16:05 ` Andrew Morton
2001-01-29 18:50 ` Rick Jones
[not found] ` <200101271854.VAA02845@ms2.inr.ac.ru>
2001-01-28 5:34 ` Andrew Morton
2001-01-28 13:37 ` Felix von Leitner
2001-01-28 14:11 ` Dan Hollis
2001-01-28 14:27 ` Andi Kleen
2001-01-29 21:50 ` Pavel Machek
2001-01-28 19:43 ` Gregory Maxwell
2001-01-28 19:48 ` Choosing Linux NICs (was: Re: sendfile+zerocopy: fairly sexy (nothing to do with ECN)) Felix von Leitner
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=Pine.GSO.4.30.0102041426180.15417-100000@shell.cyberus.ca \
--to=hadi@cyberus.ca \
--cc=andrewm@uow.edu.au \
--cc=ionut@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=raj@cup.hp.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
all inboxes | Powered by JetHome®