From: Dirk <biecie547@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: [RFT] r8169 changes against 2.6.23-rc3
Date: Mon, 20 Aug 2007 10:34:45 +0200 [thread overview]
Message-ID: <88ab4080708200134y2c05173aia5dd4e8b1a5a5712@mail.gmail.com> (raw)
In-Reply-To: <46C7ADD6.5080707@gmail.com>
On 8/19/07, Bruce Cole <bacole@gmail.com> wrote:
> So it seems that when the driver tries to queue a packet while the
> controller is busy processing the queue, the newly queued packet does
> not get noticed by the controller (until further packet activity occurs).
> Perhaps there is a problem with the memory barriers when adding to the
> TX queue, but I'm a newbie on linux kernel memory barriers.
One thing I noticed a while ago (march) is that floodpinging (ping -f)
the r8169 host from an external system also increases performance
without changing code.
My original post about the problem:
http://marc.info/?l=linux-netdev&m=117207362010321&w=2
I ended up (until now perhaps :-) with disabling the onboard nic and
adding an e1000 card.
Kind regards,
Dirk
next prev parent reply other threads:[~2007-08-20 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070818100701.GA20703@electric-eye.fr.zoreil.com>
2007-08-19 2:41 ` [RFT] r8169 changes against 2.6.23-rc3 Bruce Cole
2007-08-20 8:34 ` Dirk [this message]
2007-08-20 18:58 ` Chuck Lever
2007-08-21 19:32 Bruce Cole
2007-08-22 5:51 ` Bruce Cole
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=88ab4080708200134y2c05173aia5dd4e8b1a5a5712@mail.gmail.com \
--to=biecie547@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).