From owner-freebsd-current Thu May 21 04:45:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA22851 for freebsd-current-outgoing; Thu, 21 May 1998 04:45:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22840 for ; Thu, 21 May 1998 04:45:20 -0700 (PDT) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id NAA29389; Thu, 21 May 1998 13:42:21 +0200 (CEST) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199805211142.NAA29389@ocean.campus.luth.se> Subject: Re: and again on forwarding... In-Reply-To: <199805201832.LAA02113@bubba.whistle.com> from Archie Cobbs at "May 20, 98 11:32:41 am" To: archie@whistle.com (Archie Cobbs) Date: Thu, 21 May 1998 13:42:21 +0200 (CEST) Cc: wollman@khavrinen.lcs.mit.edu, luigi@labinfo.iet.unipi.it, eivind@yes.no, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Archie Cobbs: > Garrett Wollman writes: > > < said: > > > > >> Is that only clients in our kernel, or are there clients 'out there' > > >> which we'd have to care for, too? > > > > > i think he only refers to kernel 'clients'. Not a big deal, IMHO. > > > > Remember that one of which is the ``raw'' interface. In order to > > maintain application compatibility, the SOCK_RAW interface will need > > to do all the munging which is removed from other code paths. > > Same thing applies to ``divert'' sockets... If it's possible to move th munging from always being done, to being done only there, that would seem like progress to me. What exactly does the "munging" involve? Is it something good, or would be be nice to get rid of it alltogether? I mean, if it's of little use, but just to provide compability with older (and/or maybe non-FreeBSD) client, maybe there could also be a SOCK_RAW_NEW which simply does the same thing but skips the munging? Save thing for the divert thing, I guess, although this would be FreeBSD specific, and not entirely ancient software that uses the divert routines, so a kernel option "DIVERT_DO_MUNGING" could be added. Then the munging code moved to divert code could just be ifdef:ed on that. Or? /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message