From owner-freebsd-current Sat Apr 25 15:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05279 for freebsd-current-outgoing; Sat, 25 Apr 1998 15:40:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05269 for ; Sat, 25 Apr 1998 15:40:23 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id SAA16980; Sat, 25 Apr 1998 18:40:21 -0400 (EDT) (envelope-from wollman) Date: Sat, 25 Apr 1998 18:40:21 -0400 (EDT) From: Garrett Wollman Message-Id: <199804252240.SAA16980@khavrinen.lcs.mit.edu> To: "Justin T. Gibbs" Cc: current@FreeBSD.ORG Subject: Re: Bandwidth throttling etc. Newsgroups: pluto.freebsd.current In-Reply-To: <199804242209.QAA03142@narnia.plutotech.com> References: <199804241932.VAA22011@labinfo.iet.unipi.it> <199804242126.RAA10941@khavrinen.lcs.mit.edu> <199804242209.QAA03142@narnia.plutotech.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > How do deal with a route change between the time you determine the > target interface, ask it to allocate space for you, and construct > the packet? That's not a very common occurrence and you can just copy the packet in that case. (It's even less common when you consider that the most likely scenario is for the route to change among interfaces of the same type, which means that the new interface could be asked to ``adopt'' the old interface's buffer, and depending on the sort of hardware involved, it may be able to do so without modification.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message