From: "Madovsky" <infos@madovsky.org>
To: "Allan, Bruce W" <bruce.w.allan@intel.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: e1000e, 3.4.1, , jumbo frames are not working
Date: Wed, 20 Jun 2012 12:55:33 -0400 [thread overview]
Message-ID: <5839DCEA739B481B8C28EF3441D255EF@e1705> (raw)
In-Reply-To: <804857E1F29AAC47BF68C404FC60A1842846965C@ORSMSX102.amr.corp.intel.com>
ok thanks Bruce
----- Original Message -----
From: "Allan, Bruce W" <bruce.w.allan@intel.com>
To: "madovsky" <infos@madovsky.org>; <linux-kernel@vger.kernel.org>
Sent: Wednesday, June 20, 2012 12:45 PM
Subject: RE: e1000e, 3.4.1, , jumbo frames are not working
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> owner@vger.kernel.org] On Behalf Of madovsky
> Sent: Wednesday, June 20, 2012 7:49 AM
> To: linux-kernel@vger.kernel.org
> Subject: RE: e1000e, 3.4.1, , jumbo frames are not working
>
> it's the same on kernel 3.4.3.
> I can't activate jumbo frames
> my mobo is S5000PAL
This is already known and discussed on previous threads. If you look at
the system log file you will see a message from the driver which states
"Jumbo frames cannot be enabled when both receive checksum offload and
receive hashing are enabled. Disable one of the receive offload features
before enabling jumbos." A patch that removes this incompatibility is
currently in test here at Intel and should be passed upstream soon.
Thanks,
Bruce.
next prev parent reply other threads:[~2012-06-20 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 14:49 madovsky
2012-06-20 16:45 ` Allan, Bruce W
2012-06-20 16:55 ` Madovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-08 14:59 Denys Fedoryshchenko
2012-06-08 15:38 ` Allan, Bruce W
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=5839DCEA739B481B8C28EF3441D255EF@e1705 \
--to=infos@madovsky.org \
--cc=bruce.w.allan@intel.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®