linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: Carlo Pisani <carlojpisani@gmail.com>, linux-parisc@vger.kernel.org
Subject: Re: C8000, which is the max MTU of the built-in net card?
Date: Mon, 23 Sep 2019 07:42:45 -0400	[thread overview]
Message-ID: <905e567a-3e82-969e-8062-5dd4c712929a@bell.net> (raw)
In-Reply-To: <CA+QBN9BepXXQKksDXBn3MpRdzSq3Aq=XzTwDh_F+vVjTvnFpBg@mail.gmail.com>

On 2019-09-23 6:43 a.m., Carlo Pisani wrote:
> I need 2000 MTU, 4000 MTU, 7000 MTU, or 9000 MTU
>
> can someone check the max MTU capability of the built-in lan on a C8000?
My c8000 has an intel e1000:
[   21.140119] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI

The driver supports jumbo packets up to 0x3F00:
dave@mx3210:~/linux/linux-stable/drivers/net/ethernet/intel/e1000$ grep  MAX_JUMBO_FRAME_SIZE *
e1000_hw.h:#define MAX_JUMBO_FRAME_SIZE         0x3F00
e1000_main.c:   netdev->max_mtu = MAX_JUMBO_FRAME_SIZE - (ETH_HLEN + ETH_FCS_LEN);
e1000_main.c:           /* Capable of supporting up to MAX_JUMBO_FRAME_SIZE limit. */

Dave

-- 
John David Anglin  dave.anglin@bell.net


  reply	other threads:[~2019-09-23 11:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 21:50 Bug report (with fix) for DEC Tulip driver (de2104x.c) Arlie Davis
2019-09-17 21:28 ` Andrew Lunn
2019-09-17 21:36   ` Arlie Davis
2019-09-17 22:51     ` John David Anglin
2019-09-18  5:56       ` Helge Deller
2019-09-18 13:27         ` Thomas Bogendoerfer
2019-10-03  1:29           ` Maciej W. Rozycki
2019-09-19 20:31         ` Sven Schnelle
2019-09-23 10:43         ` C8000, which is the max MTU of the built-in net card? Carlo Pisani
2019-09-23 11:42           ` John David Anglin [this message]
2019-09-20 10:43 ` Bug report (with fix) for DEC Tulip driver (de2104x.c) Thomas Bogendoerfer

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=905e567a-3e82-969e-8062-5dd4c712929a@bell.net \
    --to=dave.anglin@bell.net \
    --cc=carlojpisani@gmail.com \
    --cc=linux-parisc@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).