From owner-freebsd-hackers Mon Jul 16 15:56:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id 3A7E237B409; Mon, 16 Jul 2001 15:56:44 -0700 (PDT) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id PAA40161; Mon, 16 Jul 2001 15:56:33 -0700 (PDT) (envelope-from rh@matriplex.com) Date: Mon, 16 Jul 2001 15:56:33 -0700 (PDT) From: Richard Hodges To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: <20010716165722.EA84737B401@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 16 Jul 2001, Bill Paul wrote: > They're "okay." The NatSemi chip has one flaw, which is that RX buffers > must be aligned on a 64-bit boundary. None of the more expensive NICs have > this restriction. Go ahead and beat me up if you have to :-) But why is there _any_ issue with RX buffer alignment? I get some mbufs and set the data pointer to any point I want, or I get a cluster, which is always on a 2k boundary. Now TX buffers are a problem - I have to take what I get and just "deal with it". If both start address and length need to be aligned, then I'm pretty much screwed - I have to copy... All the best, -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message