From: Franco Fichtner <franco@lastsummer.de>
To: Netdev <netdev@vger.kernel.org>,
jesse.brandeburg@intel.com, bruce.w.allan@intel.com
Subject: e1000e: reset of tx_queue_len
Date: Tue, 02 Mar 2010 18:44:30 +0100 [thread overview]
Message-ID: <4B8D4E7E.2000805@lastsummer.de> (raw)
Hi all,
while working on a new server, I noticed that tx_queue_len is reset
to the default of 1000 while ADDRCONF(NETDEV_CHANGE).
This happens with 2.6.30.8, but I could not see any obvious
differences to the current state of e1000e, while trying to find the
problem in the code.
The interface has been configured including a customized qlen
via /etc/network/interfaces. The ports are not connected at startup
so obviously the Kernel reports
ADDRCONF(NETDEV_UP): eth2: link is not ready
while ifconfig properly displays the customized qlen.
When plugging the server tx_queue_len is reset to 1000.
Any help is appreciated. Thanks.
Franco
next reply other threads:[~2010-03-02 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 17:44 Franco Fichtner [this message]
2010-03-02 18:27 ` e1000e: reset of tx_queue_len Brandeburg, Jesse
2010-03-02 19:52 ` Franco Fichtner
2010-03-03 14:22 ` Franco Fichtner
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=4B8D4E7E.2000805@lastsummer.de \
--to=franco@lastsummer.de \
--cc=bruce.w.allan@intel.com \
--cc=jesse.brandeburg@intel.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).