netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harsh <hanemade@gmail.com>
To: linux-net@vger.kernel.org
Cc: netdev@oss.sgi.com
Subject: help in using eth_change_mtu
Date: Mon, 24 Jan 2005 14:29:27 +0530	[thread overview]
Message-ID: <cfc9593605012400595e529682@mail.gmail.com> (raw)

Hello,
         If some extra information is required to be sent with each
packet then does that require to change Ethernet MTU 1500 to
1500-(Bytes in extra info) or its ok with 1500 value of MTU? While
checking source code of net_init.c in drivers/net dir i found one
function eth_change_mtu. I want to know does that helps? why its given
there in source code?
regards,
Harsh.

static int eth_change_mtu(struct net_device *dev, int new_mtu)
 {
        if ((new_mtu < 68) || (new_mtu > 1500))
                 return -EINVAL;
        dev->mtu = new_mtu;
        return 0;
 }

             reply	other threads:[~2005-01-24  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-24  8:59 Harsh [this message]
2005-01-25  3:46 ` help in using eth_change_mtu Neema
2005-01-25  6:20   ` Harsh

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=cfc9593605012400595e529682@mail.gmail.com \
    --to=hanemade@gmail.com \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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).