From: David Acker <dacker@roinet.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: Stephen Hemminger <shemminger@osdl.org>,
Jeff Garzik <jgarzik@pobox.com>,
dhinds@pcmcia.sourceforge.org, netdev@vger.kernel.org
Subject: Re: mii-tool gigabit support.
Date: Wed, 27 Sep 2006 16:26:06 -0400 [thread overview]
Message-ID: <451ADE5E.8000601@roinet.com> (raw)
In-Reply-To: <451AAFFE.2020607@hp.com>
Rick Jones wrote:
>> With mii-tool we can do the command below and work with a half duplex
>> hub and a full duplex switch.
>> mii-tool -A 10baseT-FD,10baseT-HD eth0
>
> Why, and how often, is that really necessary?
>
> rick jones
>
Take a wifi router with only 802.11b radios and ethernet chips that do
not support handling DMA to host memory. In this case receives from
ethernet cost a lot since the packets must be read into host memory by
the CPU (instead of written there by the adapter). Also, receiving 100
Mbit in when you only have 802.11b pipes out isn't terrible useful. UDP
blasts from ethernet can hog the CPU and with some NICs cause soft lockups.
We could just set it to 10Mbit half duplex always but two 802.11b radios
can saturate that with bidirectional traffic. We have seen failures to
send due to collisions. Thus, we would like to be able advertise 10Mb
full and half duplex so that we can get the appropriate speed when that
the neighbor device supports. We have seen various ethernet switches or
NICs (like IP video cameras with ethernet) that will not run 10Mb full
duplex but will do 100Mb full or 10Mb half.
We want it to be configurable at run time since sometimes the same
software may run on a system that has 802.11G radios and and perhaps
more capable ethernet devices. We can detect our situation in our
startup script and adjust the advertised speeds down only when needed.
-Ack
next prev parent reply other threads:[~2006-09-27 20:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 21:51 mii-tool gigabit support Stephen Hemminger
2006-09-26 21:55 ` Jeff Garzik
2006-09-26 22:09 ` Stephen Hemminger
2006-09-27 13:00 ` David Acker
2006-09-27 15:00 ` Auke Kok
2006-09-27 16:20 ` Jeff Kirsher
2006-09-27 17:08 ` Rick Jones
2006-09-27 17:50 ` Auke Kok
2006-09-27 17:57 ` Rick Jones
2006-09-27 18:05 ` Maciej W. Rozycki
2006-09-27 18:42 ` Auke Kok
2006-09-28 12:10 ` Maciej W. Rozycki
2006-09-27 20:26 ` David Acker [this message]
2006-09-27 19:24 ` dean gaudet
2006-09-27 19:31 ` Stephen Hemminger
2006-09-27 19:32 ` Auke Kok
2006-09-27 19:37 ` dean gaudet
2006-09-29 16:12 ` David Hollis
2006-09-29 17:12 ` Stephen Hemminger
2006-09-29 17:54 ` Rick Jones
2006-10-01 14:31 ` Michael Tokarev
2006-09-27 19:15 ` dean gaudet
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=451ADE5E.8000601@roinet.com \
--to=dacker@roinet.com \
--cc=dhinds@pcmcia.sourceforge.org \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=shemminger@osdl.org \
/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;
as well as URLs for NNTP newsgroup(s).