Christian Schmid wrote:
Hello.
After weeks of work, I can now give a detailed report about the bug and
when it appears:
Attached is another traffic-image. This one is with 2.6.10 and a 3/1
split, preemtive kernel, so all defaults.
What are the units on your graph. You say "MB" several places, but
do you mean Mb (ie, Mega-bit) instead?
I have a tool that can also generate TCP traffic on a large number of
sockets. If I can understand what you are trying to do, I may be able
to reproduce the problem. My biggest machine at present has only
2GB of RAM, however...not sure if that matters or not.
Are you sending traffic in only one direction, or more of a full-duplex
configuration? Is each socket running the same bandwidth? What is this
bandwidth? Are you setting the send & rcv buffers in the socket creation
code? (To what values if so?) How many bytes are you sending with each
call to write()/sendto() whatever?
Is there any significant latency between your sender and receiver machine?
If so, how much?
What is the physical transport...GigE? 1500 MTU?
Thanks,
Ben
--
Ben Greear <[EMAIL PROTECTED]>
Candela Technologies Inc http://www.candelatech.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
