From: Nix <nix@esperi.org.uk>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: e1000-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
netdev <netdev@vger.kernel.org>,
bruce.w.allan@intel.com
Subject: Re: 2.6.31 regression: e1000e jumbo frames no longer work: 'Unsupported MTU setting'
Date: Mon, 28 Sep 2009 21:51:18 +0100 [thread overview]
Message-ID: <87ab0elrnd.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <5f2db9d90909261914l3a927f4cya1dc5e4548688bce@mail.gmail.com> (Alexander Duyck's message of "Sat, 26 Sep 2009 19:14:55 -0700")
On 27 Sep 2009, Alexander Duyck said:
> It looks like the problem is that the 82574 and 82583 seem to have
> their max_hw_frame_size values swapped. You might try applying the
> patch below. I am not sure if it will apply since I hand generated it
Applies fine: works fine. Thank you!
> using the git patch that seems to have introduced the problem, and I
> am sending the patch through an untested account that may mangle the
> patch.
Unmangled.
> I will see about submitting an official patch for this
> sometime next few days.
I wonder if this belongs in -stable? People with an 82574 who are using
jumbo frames may well find their networks not coming up, if like me
they set a bunch of properties in one /sbin/ip call.
WARNING: multiple messages have this Message-ID (diff)
From: Nix <nix@esperi.org.uk>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: e1000-devel@lists.sourceforge.net,
netdev <netdev@vger.kernel.org>,
bruce.w.allan@intel.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.31 regression: e1000e jumbo frames no longer work: 'Unsupported MTU setting'
Date: Mon, 28 Sep 2009 21:51:18 +0100 [thread overview]
Message-ID: <87ab0elrnd.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <5f2db9d90909261914l3a927f4cya1dc5e4548688bce@mail.gmail.com> (Alexander Duyck's message of "Sat, 26 Sep 2009 19:14:55 -0700")
On 27 Sep 2009, Alexander Duyck said:
> It looks like the problem is that the 82574 and 82583 seem to have
> their max_hw_frame_size values swapped. You might try applying the
> patch below. I am not sure if it will apply since I hand generated it
Applies fine: works fine. Thank you!
> using the git patch that seems to have introduced the problem, and I
> am sending the patch through an untested account that may mangle the
> patch.
Unmangled.
> I will see about submitting an official patch for this
> sometime next few days.
I wonder if this belongs in -stable? People with an 82574 who are using
jumbo frames may well find their networks not coming up, if like me
they set a bunch of properties in one /sbin/ip call.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
next prev parent reply other threads:[~2009-09-28 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 11:16 2.6.31 regression: e1000e jumbo frames no longer work: 'Unsupported MTU setting' Nix
2009-09-27 2:14 ` Alexander Duyck
2009-09-27 2:14 ` Alexander Duyck
2009-09-28 20:51 ` Nix [this message]
2009-09-28 20:51 ` Nix
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=87ab0elrnd.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=alexander.duyck@gmail.com \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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 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.