How to figure this out for yourself:
Look at net/sched/sch_plug.c, which is a pretty simple qdisc
(transmit packets until a plug request is recieved, then queue until
unplugged). In particular, look at plug_enqueue() to see what happens
when q-limit is exceeded, and plug_init() to see
Hi!
On 14:11 Sat 13 Apr , christian...@wwad.de wrote:
Hi All,
can someone please explain me, how the kernel handles different
transfer rates of different net_devices? Or in other words: How does
the systemcall send() know, when to block?
An example:
cat /dev/zero | pv | nc -u
On Sun, 14 Apr 2013 10:09:54 +0200, mic...@michaelblizek.twilightparadox.com
said:
This is not what I meant. When the qdisc has a size of say 256KB and the
socket memory is, say 128kb, the socket memory limit will be reached before
the qdisc limit and the socket will sleep. But when the
Hi All,
can someone please explain me, how the kernel handles different
transfer rates of different net_devices? Or in other words: How does
the systemcall send() know, when to block?
An example:
cat /dev/zero | pv | nc -u someip
will show different throughput speeds depending on the network
