From: Rick Jones <rick.jones2@hp.com>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: L F <lfabio.linux@gmail.com>,
James Chapman <jchapman@katalix.com>,
netdev@vger.kernel.org
Subject: Re: e1000 driver and samba
Date: Mon, 17 Sep 2007 11:02:58 -0700 [thread overview]
Message-ID: <46EEC152.8090005@hp.com> (raw)
In-Reply-To: <46ECB95F.2090100@intel.com>
Kok, Auke wrote:
> L F wrote:
>
>>>>>>tx_deferred_ok: 486
>>>
>>>this one I wonder about, and might cause delays, I'll have to look
>>>up what it exactly could implicate though.
>>
>>Please do and let me know. samba 3.0.26 helped, but the issue is
>>still there.
>
>
> ok, from the spec: tx_deferred_ok is what is in the DC stats register. DC stands
> for "Deferred Count". This initially is meant to track how often the TX unit cannot
> send because the medium is busy in a Half-Duplex link state.
>
> To me it suggests that your speed is not full-duplex. Check `ethtool eth0` output
> and see if your link is full duplex or not. also check previous kernel messages
> and see what the e1000 driver posted there for link speed messages (as in "e1000:
> Link is UP speed XXX duplex YYY")
Shouldn't there then have been at least _some_ collisions reported in
the stats? And perhaps some late collisions?
rick jones
next prev parent reply other threads:[~2007-09-17 18:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 2:04 e1000 driver and samba L F
2007-09-14 17:18 ` Kok, Auke
2007-09-14 18:40 ` L F
2007-09-14 20:59 ` Kok, Auke
2007-09-15 0:37 ` L F
2007-09-15 5:09 ` Bill Fink
2007-09-15 12:27 ` L F
2007-09-15 12:44 ` L F
2007-09-15 17:44 ` James Chapman
2007-09-15 19:07 ` Kok, Auke
2007-09-16 4:06 ` L F
2007-09-16 5:04 ` Kok, Auke
2007-09-17 16:42 ` L F
2007-09-17 17:02 ` Kok, Auke
2007-09-17 18:58 ` L F
2007-09-17 21:01 ` Brandeburg, Jesse
2007-09-18 6:03 ` Bill Fink
2007-09-18 7:45 ` Urs Thuermann
2007-09-18 8:47 ` Bill Fink
2007-09-18 13:39 ` Florian Weimer
2007-09-18 16:32 ` L F
2007-09-18 17:04 ` Tantilov, Emil S
2007-09-19 14:53 ` L F
2007-09-20 2:51 ` Bill Fink
2007-09-21 14:08 ` L F
2007-09-20 4:53 ` Bill Fink
2007-09-18 16:44 ` Bill Fink
2007-09-17 18:02 ` Rick Jones [this message]
2007-09-17 18:51 ` Kok, Auke
2007-09-16 16:24 ` James Chapman
2007-09-16 20:03 ` Kok, Auke
2007-09-16 4:07 ` L F
2007-09-14 18:26 ` Francois Romieu
2007-09-14 18:41 ` L F
-- strict thread matches above, loose matches on Subject: below --
2007-09-20 23:30 Bruce Cole
2007-09-21 14:13 ` L F
2007-09-21 18:21 ` Bruce Cole
2007-09-21 21:49 ` Francois Romieu
2007-09-21 22:01 ` Bruce Cole
2007-09-21 22:41 ` Francois Romieu
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=46EEC152.8090005@hp.com \
--to=rick.jones2@hp.com \
--cc=auke-jan.h.kok@intel.com \
--cc=jchapman@katalix.com \
--cc=lfabio.linux@gmail.com \
--cc=netdev@vger.kernel.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).