From owner-freebsd-hackers Tue Feb 9 13:52:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12976 for freebsd-hackers-outgoing; Tue, 9 Feb 1999 13:52:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12968 for ; Tue, 9 Feb 1999 13:52:32 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA09844; Tue, 9 Feb 1999 13:47:36 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdRy9842; Tue Feb 9 21:47:35 1999 Date: Tue, 9 Feb 1999 13:47:32 -0800 (PST) From: Julian Elischer To: Larry Lile cc: hackers@FreeBSD.ORG Subject: Re: NFS Alignment? was (Re: Why did this panic?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ethernet headers are 14 bytes they are trying to allign the IP header on a word boundary.. julian On Tue, 9 Feb 1999, Larry Lile wrote: > > By the way, is the "m->m_data += 2;" still a neccesary evil to > apease NFS? I have always seen it in drivers but I never understood > why it was there or if I really needed to follow it. > > from if_ed.c: 2727-2732 > > /* > * The +2 is to longword align the start of the real packet. > * This is important for NFS. > */ > m->m_data += 2; > eh = mtod(m, struct ether_header *); > > Larry Lile > lile@stdio.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message