From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: LinuxPPC-Embedded <linuxppc-embedded@ozlabs.org>
Cc: Darcy Watkins <DWatkins@tranzeo.com>
Subject: Re: Ethernet Jumbo Frames
Date: Tue, 01 Apr 2008 10:54:38 +0200 [thread overview]
Message-ID: <47F1F84E.8030001@aimvalley.nl> (raw)
In-Reply-To: <D61182AC8012EA4EBC531B3AF23BE109582F00@tranzeo-mail2.12stewart.tranzeo.com>
We've done it for our 2.4 based kernel that runs on a Freescale MPC8270.
10/100/1000 doesn't really make any difference. For us the trick was to
support receving jumbo frames in multiple RX BufDescriptors (because our
MPC8270 FCC eth driver pre-allocates 2k buffers per RX BD).
For transmitting hardly any changes were necessary.
From linux (driver) standpoint there should be no problems,
the question is whether your ethernet MAC (IBM EMAC) properly supports it.
hth,
N. van Bolhuis.
Darcy Watkins wrote:
> Has anyone on this list ever been given a requirement to implement
> support for ethernet frames larger than the standard MTU of 1500? ...
>
> ... for normal 10/100 Ethernet? ... not gigabit.
>
> The application is to support certain encapsulation protocols without
> imposing smaller than 1500 byte MTU restrictions on the innermost
> protocol.
>
> I have been tasked to investigate this for a system based on PPC405EP.
> Can it be done using the IBM EMAC, Linux drivers, etc?
>
> Regards,
>
> Darcy
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
--
This message has been scanned for viruses and is believed to be clean
next prev parent reply other threads:[~2008-04-01 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 20:47 Ethernet Jumbo Frames Darcy Watkins
2008-04-01 8:54 ` Norbert van Bolhuis [this message]
2008-04-02 21:15 ` Rick Moleres
2008-04-02 21:32 ` Darcy Watkins
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=47F1F84E.8030001@aimvalley.nl \
--to=nvbolhuis@aimvalley.nl \
--cc=DWatkins@tranzeo.com \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.