From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Sinisa Bandin <sinisa@bandin.homelinux.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
samba@lists.samba.org, submit@bugs.debian.org,
contact_us@realtek.com
Subject: Re: [Samba] 2.6.22/realtek bug in hardware, any kernel work-around?
Date: Sun, 30 Sep 2007 16:42:04 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0709301639290.10027@p34.internal.lan> (raw)
In-Reply-To: <4700092C.5060805@bandin.homelinux.com>
On Sun, 30 Sep 2007, Sinisa Bandin wrote:
>
> Justin Piszcz wrote:
>> Package: samba
>> Version: 3.0.26a-1
>>>
>>> Kernel: 2.6.22
>>>
>>> samba 3.0.26a-1 performance < 900 KiB/s, but FTP = 30-90 MiB/s
>>>
>>> Let me start out by saing this is an oddball problem:
>>>
>>> SAMBA:
>>> LINUX -> WINDOWS = < 900 KiB/s (varies between 100 - 900 KiB/s)
>>> WINDOWS -> LINUX = 30-90 MiB/s (always)
>>>
>>> FTP:
>>> Either direction, 30-90 MiB/s (always)
>>>
>>> I do not see any nasty errors in the logs even with verbose = 5.
>>>
>>> Any ideas here? I am not using any special options.
>>
>> I found out that poor smb performance is related to a broken udp-perfomance
>> of the 8169 NIC in outgoing udp.
>> But, only in Gb Mode of the 8169 NIC, with 100Mbps it is ok.
>>
> I had exactly the same problem with 100Mb/s also.
>
> Solved by disabling onboard LAN interface and inserting (US Robotics) Realtek
> 8139 based card (10/100 Mbps).
>
> Best regards,
> Sinisa Bandin
>
Thank you for your response, so the bottom line is Realtek 1Gbps NICs are
unreliable. Wonder what Realtek has to say about it if they even respond,
added them to cc list.
Justin.
next prev parent reply other threads:[~2007-09-30 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0709291349160.5726@p34.internal.lan>
2007-09-29 18:37 ` Justin Piszcz
2007-09-30 20:38 ` [Samba] " Sinisa Bandin
2007-09-30 20:42 ` Justin Piszcz [this message]
2007-09-30 20:50 ` Sinisa Bandin
2007-10-03 20:37 ` 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=Pine.LNX.4.64.0709301639290.10027@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=contact_us@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=samba@lists.samba.org \
--cc=sinisa@bandin.homelinux.com \
--cc=submit@bugs.debian.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
all inboxes | Powered by JetHome®