> It is also useful to have both client and server stats.
> BTW, since the laptop (with the 3C card) is the client, the SG
> shouldnt kick in at all.
The `client' here is doing the sendfiling, so yes, the
gathering occurs on the client.
> > The test tool is, of course, documented [ :-)/2 ]. It's at
> > http://www.uow.edu.au/~andrewm/linux/#zc
> I'll give this a shot later. Can you try with the sendfiled-ttcp?
hmm.. I didn't bother with TCP_CORK because the files being
sent are "much" larger than a frame. Guess I should.
The problem with things like ttcp is the measurement of CPU load.
If your network is so fast that your machine can't keep up then
fine, raw throughput is a good measure. But if the link is saturated
then normal process accounting doesn't cut it.
For example, at 100 mbps, `top' says ttcp is chewing 4% CPU. But guess
what? A low-priority process running on the same machine is in fact
slowed down by 30%. top lies. Most of the cost of the networking layer
is being accounted to swapper, and lost. And who accounts for cache
eviction, bus utilisation, etc. We're better off measuring what's
left behind, rather than measuring what is consumed.
You can in fact do this with ttcp: run it with a super-high priority
and run a little task in the background (dummyload.c in the above
tarball does this). See how much the dummy task is slowed down
wrt an unloaded system. It gets tricky on SMP though.