| To: | kuznet@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: conflicting alignment requirements |
| From: | Ralf Baechle <ralf@xxxxxxxxxxx> |
| Date: | Wed, 1 Aug 2001 04:36:38 +0200 |
| Cc: | Jacob Avraham <jacoba@xxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <200107311712.VAA04463@xxxxxxxxxxxxx>; from kuznet@xxxxxxxxxxxxx on Tue, Jul 31, 2001 at 09:12:22PM +0400 |
| References: | <EJEHILNJPONOHGEOJKICAEDDCAAA.jacoba@xxxxxxxxx> <200107311712.VAA04463@xxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Tue, Jul 31, 2001 at 09:12:22PM +0400, kuznet@xxxxxxxxxxxxx wrote: > > copy the packet to a fresh skb (rx_copybreak = 0), the packet will > > traverse the net layer with unalinged IP header. > > Doing this for an arch which traps wrong alignment, you can expect > everything (except for crash, which could be bug). Afaik all such architectures have exception handlers to complete the access transparently in software. Such an access is very slow so where more frequent unaligned accesses are expected there are get_unaligned() and put_unaligned(). Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: IPv6 fragmentation and IPv6 header parsing, Brad Chapman |
|---|---|
| Next by Date: | kernel module problem., Kamal Deep Dham |
| Previous by Thread: | Re: conflicting alignment requirements, kuznet |
| Next by Thread: | airport reset on iBook2, Ethan Blanton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |