All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Oeser <netdev@axxeo.de>
To: thockin@hockin.org
Cc: Jeff Garzik <jgarzik@pobox.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] natsemi: Messages being noisy
Date: Fri, 15 Sep 2006 10:11:38 +0200	[thread overview]
Message-ID: <200609151011.39096.netdev@axxeo.de> (raw)
In-Reply-To: <20060914154607.GA7576@hockin.org>

Hi Tim,
Hi Jeff,

thockin@hockin.org wrote:
> On Thu, Sep 14, 2006 at 05:39:08PM +0200, Ingo Oeser wrote:
> > Ingo Oeser wrote:
> > > I  get the following message when trying to transfer big files 
> > > (via FTP or SCP) since Linux 2.6.16.27. It didn't happen with Linux 2.6.13.4.
> > > 
> > > [702238.242237] eth1: increased tx threshold, txcfg 0xd0f01008.
> > > [702238.242649] eth1: increased tx threshold, txcfg 0xd0f0100a.
> > 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..

Will implementing "ethtool_ringparam" be the right thing for this?

Or is there simply no ethtool mechanism for setting up thresholds, yet?

If not, I would simply like to have my original pr_debug patch included. 
The actual value of the tx threshhold can be queried 
via "ethtool -d eth0" already.

What do you think?


Regards

Ingo Oeser

  reply	other threads:[~2006-09-15  8:12 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 [this message]
2006-09-15 10:52     ` Mark Brown

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=200609151011.39096.netdev@axxeo.de \
    --to=netdev@axxeo.de \
    --cc=jgarzik@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.