From: Mark Brown <broonie@sirena.org.uk>
To: thockin@hockin.org
Cc: Ingo Oeser <netdev@axxeo.de>, netdev@vger.kernel.org
Subject: Re: [PATCH] natsemi: Messages being noisy
Date: Fri, 15 Sep 2006 11:52:36 +0100 [thread overview]
Message-ID: <20060915105232.GA3645@sirena.org.uk> (raw)
In-Reply-To: <20060914154607.GA7576@hockin.org>
On Thu, Sep 14, 2006 at 08:46:07AM -0700, thockin@hockin.org wrote:
> On Thu, Sep 14, 2006 at 05:39:08PM +0200, Ingo Oeser wrote:
> > Is it possible to have the maximum value right from the start?
> > May I tune it somewhere to be the maximum from the start?
> This will (if I recall) increase transmit latency. It's a fine line. You
> might tune it up, but this fallback path probably should not be removed..
Yes, raising the limit there will increase transmit latency since it
causes the chip to wait for more data to be DMAed before it begins
pushing the frame out. I guess the dropped packet could be worked
around by resubmitting the dropped packet when we reconfigure the chip,
though obviously that's not ideal.
It would be interesting to understand what caused this to start
happening. The main change in natsemi itself between 2.6.13.4 and
2.6.16.27 is the introduction of NAPI although it could be some other
change causing PCI bandwidth to become more scarce.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
prev parent reply other threads:[~2006-09-15 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 13:28 [PATCH] natsemi: Messages being noisy Ingo Oeser
2006-09-14 15:39 ` Ingo Oeser
2006-09-14 15:46 ` thockin
2006-09-15 8:11 ` Ingo Oeser
2006-09-15 10:52 ` Mark Brown [this message]
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=20060915105232.GA3645@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=netdev@axxeo.de \
--cc=netdev@vger.kernel.org \
--cc=thockin@hockin.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).