From: john@BlueSkyTours.com
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Bruce Cole <bacole@gmail.com>, netdev@vger.kernel.org
Subject: Re: r8169: slow samba performance
Date: Tue, 4 Sep 2007 15:00:11 -0600 (MDT) [thread overview]
Message-ID: <Pine.SOC.4.64.0709041457200.871@katana> (raw)
In-Reply-To: <20070904203742.GB31783@electric-eye.fr.zoreil.com>
On Tue, 4 Sep 2007, Francois Romieu wrote:
> john@BlueSkyTours.com <john@BlueSkyTours.com> :
> [...]
>> 20070903-2.6.23-rc5-r8169-test.patch applied against 2.6.23-rc5 works fine.
>> Performance is acceptable.
>
> Does "acceptable" mean that there is a noticeable difference when compared
> to the patch based on a busy-waiting loop ?
Without this patch, latency in bringing up emacs, or in display of pages in
firefox is extremely high. With the patch, latency is pretty much what I
see when using an old tulip based NIC.
Is there a specific test you wish me to try?
>> Would you like me to *just* try patches 1 & 2, to help narrow down anything?
>
> I expect patch #2 alone to be enough to enhance the performance. If it gets
> proven, the patch would be a good candidate for a quick merge upstream.
Okay, I will build another kernel with just #2 applied.
John
next prev parent reply other threads:[~2007-09-04 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 16:39 r8169: slow samba performance Bruce Cole
[not found] ` <20070822182116.GA5445@csy.ca>
2007-08-22 19:46 ` Bruce Cole
2007-08-27 22:34 ` john
2007-09-03 21:03 ` Francois Romieu
2007-09-04 20:04 ` john
2007-09-04 20:37 ` Francois Romieu
2007-09-04 21:00 ` john [this message]
2007-09-04 21:51 ` Bruce Cole
-- strict thread matches above, loose matches on Subject: below --
2007-09-09 7:44 David Madsen
2007-09-09 15:33 ` Francois Romieu
2007-09-14 1:31 ` David Madsen
2007-09-16 1:11 ` David Madsen
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.SOC.4.64.0709041457200.871@katana \
--to=john@blueskytours.com \
--cc=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).