From: Jay Cliburn <jacliburn@bellsouth.net>
To: netdev@vger.kernel.org
Subject: Via Velocity minimum MTU size
Date: Sun, 21 May 2006 21:56:49 -0500 [thread overview]
Message-ID: <1148266609.2329.16.camel@osprey.hogchain.net> (raw)
Hello,
I was advised by someone on the fedora-devel-list to post my question
here.
I'm trying to set the MTU size on my Via Velocity 6122 Gbit adapter from
the default of 1500 down to 1492, but I keep getting this error:
[root@osprey ~]# ifconfig eth0 mtu 1492
SIOCSIFMTU: Invalid argument
Turns out that via-velocity.h defines the minimum MTU at 1500 bytes.
#define VELOCITY_MIN_MTU (1514-14)
#define VELOCITY_MAX_MTU (9000)
And via-velocity.c enforces the limit.
if ((new_mtu < VELOCITY_MIN_MTU) || new_mtu > (VELOCITY_MAX_MTU)) {
VELOCITY_PRT(MSG_LEVEL_ERR, KERN_NOTICE "%s: Invalid MTU.\n",
vptr->dev->name);
return -EINVAL;
}
This is an Abit AV8 motherboard with an Athlon64 3000+ cpu running
Fedora Core 5, kernel 2.6.16-1.2111_FC5 x86_64.
Can someone please explain why the driver might constrain the NIC to a
minimum MTU size of 1500?
Thanks,
Jay
next reply other threads:[~2006-05-22 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 2:56 Jay Cliburn [this message]
2006-05-22 21:25 ` Via Velocity minimum MTU size Francois Romieu
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=1148266609.2329.16.camel@osprey.hogchain.net \
--to=jacliburn@bellsouth.net \
--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