Herbert Xu wrote:
Chris Friesen <[EMAIL PROTECTED]> wrote:
Looking at the page-splitting code, it says "82571 and greater support
packet-split...". We're running the 82546GB device. Looks like it
won't help me.
Well, time to fork out for a new card then :)
I wish. This is an embedded
Chris Friesen <[EMAIL PROTECTED]> wrote:
> Herbert Xu wrote:
>
>> Either upgrade your kernel or backport the page-splitting code in the
>> current tree. That's really the only sane solution for jumbo packets.
>
> Looking at the page-splitting code, it says "82571 and greater support
> packet-sp
On Fri, Jun 30, 2006 at 05:35:34PM -0600, Chris Friesen ([EMAIL PROTECTED])
wrote:
> Evgeniy Polyakov wrote:
>
> >It definitely will.
> >Packet split in hardware means separating data and headers into
> >different pages in different reads, while software page split means that
> >skb has a list o
On 6/30/06, Chris Friesen <[EMAIL PROTECTED]> wrote:
Evgeniy Polyakov wrote:
> It definitely will.
> Packet split in hardware means separating data and headers into
> different pages in different reads, while software page split means that
> skb has a list of fragments where part of the packet w
Evgeniy Polyakov wrote:
It definitely will.
Packet split in hardware means separating data and headers into
different pages in different reads, while software page split means that
skb has a list of fragments where part of the packet will be DMAed, so
jumbo frame will be converted into several
On Fri, Jun 30, 2006 at 11:53:36AM -0600, Chris Friesen ([EMAIL PROTECTED])
wrote:
> >Either upgrade your kernel or backport the page-splitting code in the
> >current tree. That's really the only sane solution for jumbo packets.
>
> Looking at the page-splitting code, it says "82571 and greater
Herbert Xu wrote:
Either upgrade your kernel or backport the page-splitting code in the
current tree. That's really the only sane solution for jumbo packets.
Looking at the page-splitting code, it says "82571 and greater support
packet-split...". We're running the 82546GB device. Looks lik
Chris Friesen <[EMAIL PROTECTED]> wrote:
>
> Anyone have any suggestions on how to improve this? Upgrading kernels
> isn't an option. I could port back the copybreak stuff fairly easily.
Either upgrade your kernel or backport the page-splitting code in the
current tree. That's really the only
