From owner-freebsd-hackers Sat Mar 25 16:54:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id D303937B6AD for ; Sat, 25 Mar 2000 16:54:06 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id SAA29089; Sat, 25 Mar 2000 18:56:42 -0600 (CST) (envelope-from jlemon) Date: Sat, 25 Mar 2000 18:56:42 -0600 (CST) From: Jonathan Lemon Message-Id: <200003260056.SAA29089@prism.flugsvamp.com> To: justin@apple.com, hackers@freebsd.org Subject: Re: Request for review (HW checksum patches) X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >> From: Jonathan Lemon >> Date: Sat, 25 Mar 2000 13:35:53 -0600 >> To: net@FreeBSD.ORG, hackers@FreeBSD.ORG >> Subject: Request for review (HW checksum patches) >> X-Mailer: Mutt 1.0pre2i >> Delivered-to: freebsd-net@freebsd.org >> X-Loop: FreeBSD.org >> >> I have a set of patches which allows offloading checksums to >> NICs which support it (right now, only the Alteon based cards). >> The patch is at . > >This prompts a question on a related issue: there seems to be an increase >in support of protocol operations on NICs (e.g., tickle/keep-alive support >while the system is sleeping; IPSec; ...). Is there enough there to let us >build a general mechanism for communication between stack and driver for >this sort of thing (e.g., a "meta-data" slot in the packet header which >points to an mbuf, or other structure, that contains the details)? The patches I have were designed to solve a single problem, just checksum offloading. There are enough bits left in the new flag field that you could use for something else, I don't know enough about what you'd want to do to say if it's enough for a general mechanism. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message