netdev
[Top] [All Lists]

RE: conflicting alignment requirements

To: "Network Development List" <netdev@xxxxxxxxxxx>
Subject: RE: conflicting alignment requirements
From: "Jacob Avraham" <jacoba@xxxxxxxxx>
Date: Wed, 25 Jul 2001 17:40:17 +0200
Cc: "Network Development List" <netdev@xxxxxxxxxxx>
Importance: Normal
In-reply-to: <20010725151707.44709@xxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx

> -----Original Message-----
> From: Andi Kleen [mailto:ak@xxxxxx]
> Sent: Wednesday, July 25, 2001 3:17 PM
> To: Jacob Avraham
> Cc: Network Development List
> Subject: Re: conflicting alignment requirements
> 
> 
> On Wed, Jul 25, 2001 at 12:57:37AM +0200, Jacob Avraham wrote:
> > I noticed that some ethernet drivers, like the tulip,
> > require that the receive buffers be 4 byte align
> > (I believe due to h/w constrains).
> > On the  other hand, some upper layer code, like tc
> > (for non x86/68k), checks if the IP header is 4 byte align,
> > and if not, doesn't handle the packet.
> > So it looks like tc and tulip can not be used on other architectures.
> > 
> > Has this been discussed before and if yes what was the outcome?
> > In the short term, would that be OK to remove this restriction
> > from tc?
> 
> If some network stack code checks the alignment and reject unaligned
> packets it is a bug. Could you tell exactly which code does that?
> 
> -Andi
> 
> 

<Prev in Thread] Current Thread [Next in Thread>