From: Young Koh <young.koh@gmail.com>
To: Nuutti Kotivuori <naked@iki.fi>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: tun/tap network throughput problem
Date: Tue, 8 Mar 2005 11:42:20 -0500 [thread overview]
Message-ID: <3524bf1f050308084246dc9341@mail.gmail.com> (raw)
In-Reply-To: <87psya4btv.fsf@aka.i.naked.iki.fi>
Hi,
thank you for your reply.
> Remember to check the packet drop readings from inside the UML kernel
> as well as on all interfaces on the host side.
i checked the packet drop reading from UML kernel shell, but it still
shows no packet dropping.
> watch -n1 tc -d -s qdisc show
so, i ran tc in the host machine as you suggested, and it reported
some packets are being dropped in eth0. (even though the stat from
/sbin/ifconfig still didn't report any packet drops)
$watch -n1 tc -d -s qdisc show
qdisc pfifo_fast 0: dev eth0 [Unknown qdisc, optlen=20]
Sent 18300080724 bytes 13121666 pkts (dropped 1328688, overlimits 0)
qdisc pfifo_fast 0: dev tap0 [Unknown qdisc, optlen=20]
Sent 7664312 bytes 17650 pkts (dropped 0, overlimits 0)
---
i saw around 50,000 packet droppings out of around 240,000 packets.
then, i tried larger txqueues in eth0. as i configured with the larger
txqueue, the less packet droppings i got.
so, when i finally i assigned 50,000 for txqueuelen in the eth0. there
was no packet dropping. and the final rates are, sending rate =
~800Mbits, and receiving rate(in another machine) = ~650Mbits
it seems to me that UML was sending too fast for eth0 to handle, so
there were packet droppings because of the rate difference between
tap0 and eth0. hrmm.. is there any flow control between tap0 and eth0?
(i guess not, from the result, though)
even in host Linux kernel, how is flow control managed between native
Linux and eth0? i mean, what happens if (host) Linux kernel sends too
many packets(or socket buffers) to eth0 device?
thank you very much,
-Young
>
> Since you are sending large packets, I would suggest making sure that
> all involved interfaces have large enough txqueues.
>
> You can monitor queue buildup by:
>
> watch -n1 tc -d -s qdisc show
>
> There should be no places for silent drops in the packet handling
> things - go around and try to find where the packets are dropping (or
> being queued forever).
>
> -- Naked
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> User-mode-linux-devel mailing list
> User-mode-linux-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-03-08 16:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 20:56 [uml-devel] tun/tap network throughput problem Young Koh
2005-03-08 11:27 ` [uml-devel] " Nuutti Kotivuori
2005-03-08 16:42 ` Young Koh [this message]
2005-03-08 17:46 ` Nuutti Kotivuori
2005-03-08 18:51 ` Young Koh
2005-03-09 9:25 ` Nuutti Kotivuori
2005-03-09 11:48 ` Nuutti Kotivuori
2005-03-10 17:39 ` Rob Landley
2005-03-09 19:29 ` [uml-devel] " Blaisorblade
2005-03-09 21:46 ` Young Koh
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=3524bf1f050308084246dc9341@mail.gmail.com \
--to=young.koh@gmail.com \
--cc=naked@iki.fi \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.