From: Bruce Cole <bacole@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org, bacole@gmail.com
Subject: Re: e1000 driver and samba
Date: Fri, 21 Sep 2007 15:01:47 -0700 [thread overview]
Message-ID: <46F43F4B.7090903@gmail.com> (raw)
In-Reply-To: <20070921214916.GA2386@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Bruce Cole <bacole@gmail.com> :
>
>>> If you look for it on the Realtek cards, there had been sporadic
>>> Nissues up to late 2005. The solution posted universally was 'change
>>> card'.
>>>
>> Yes, that *was* the common recommendation.
>>
>
> There was no such thing as a universal solution to sporadic issues.
>
I made no such claim. I do claim the realtek samba et all issues are
not sporadic however. In fact the
common problem is readily reproducible as has been shown.
> [...]
>
>> I suspect the root problem is the driver isn't properly locking
>> the TX queue.
>>
>
> Can you be more specific ?
>
Yes per the reference I gave:
http://www.spinics.net/lists/netdev/msg40384.html
"Now since this change heals the TX queue stall, it would seem that the real
underlying problem involves a race condition with enqueueing to the TX queue
while the controller is processing the queue. The ultimate fix for that
I bet is either to address locking at TX enqueue time, or there is a
controller bug. Any clarification from realtek on the necessary
processing for the NPQ bit, or
a known controller problem?
PS: I've also received private email that this problem pertains to video
streaming (to a Kiss DVD player) not just samba or X11 traffic. Basically
most all high-level TCP based protocols are affected it seems. This serious
performance problem should be considered to impact a lot more than just
samba
users."
I could probably help fix the underlying problem but I didn't
receive any response to my post quoted above.
next prev parent reply other threads:[~2007-09-21 22:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 23:30 e1000 driver and samba 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 [this message]
2007-09-21 22:41 ` Francois Romieu
-- strict thread matches above, loose matches on Subject: below --
2007-09-14 2:04 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
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
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=46F43F4B.7090903@gmail.com \
--to=bacole@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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).