public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "D. Stussy" <spam+newsgroups@bde-arc.ampr.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Intel e1000 ethernet device, change in kernel v3.4, and jumbo  frames setting DENIED.
Date: Thu, 5 Jul 2012 12:55:31 -0700	[thread overview]
Message-ID: <jt4rfk$enl$1@snarked.org> (raw)
In-Reply-To: <jjGoO-7l0-19@gated-at.bofh.it>

"Henrique de Moraes Holschuh"  wrote in message 
news:jjGoO-7l0-19@gated-at.bofh.it...

On Wed, 04 Jul 2012, D. Stussy wrote:
> There has been some changes to the driver such that things like
> checksum verification is offloaded from the CPU.  However, this
> blocks the ability to set a jumbo frame.  The kernel does record an
> error indicating that checksum offloading need be disabled fro jumbo
> frame MTU sizes to be used.  My e1000 interfaces use the 82574L
> chipset.
>
> 1)  Was this an intentional change?

Yes, but I understand Intel is trying to come up with a way not to need it.

> 2)  How do I disable that function so I can set jumbo frames with
> "ifconfig" or "ip"?  I simply don't know what setting I need to
> pass.

ethtool can do it.  Check its manpage, it can manipulate the various NIC
offload engines, as well as other parameters such as dma ring buffer size,
etc.
=====================
I'll look into it.  Thanks. 


       reply	other threads:[~2012-07-05 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jjE3E-5PM-29@gated-at.bofh.it>
     [not found] ` <jjGoO-7l0-19@gated-at.bofh.it>
2012-07-05 19:55   ` D. Stussy [this message]
2012-07-05 23:53   ` Intel e1000 ethernet device, change in kernel v3.4, and jumbo frames setting DENIED D. Stussy
2012-07-04 19:56 D. Stussy
2012-07-04 22:33 ` Henrique de Moraes Holschuh

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='jt4rfk$enl$1@snarked.org' \
    --to=spam+newsgroups@bde-arc.ampr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=replies+newsgroups@kd6lvw.ampr.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