From owner-svn-src-all@FreeBSD.ORG Sun Mar 29 08:07:05 2015 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 811BCE4A; Sun, 29 Mar 2015 08:07:05 +0000 (UTC) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 326E7EBB; Sun, 29 Mar 2015 08:07:05 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Yc8FI-0008Zf-Lt; Sun, 29 Mar 2015 11:07:00 +0300 Date: Sun, 29 Mar 2015 11:07:00 +0300 From: Slawa Olhovchenkov To: Benjamin Kaduk Subject: Re: svn commit: r280759 - head/sys/netinet Message-ID: <20150329080700.GM23643@zxy.spb.ru> References: <201503271326.t2RDQxd3056112@svn.freebsd.org> <20150328083443.GV64665@FreeBSD.org> <20150328172313.GC51048@funkthat.com> <20150328181833.GX64665@FreeBSD.org> <20150328204333.GF51048@funkthat.com> <20150328213403.GB74532@zxy.spb.ru> <20150329011534.GH51048@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: "src-committers@freebsd.org" , John-Mark Gurney , Fabien Thomas , Gleb Smirnoff , "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 08:07:05 -0000 On Sat, Mar 28, 2015 at 11:22:16PM -0400, Benjamin Kaduk wrote: > On Sat, Mar 28, 2015 at 9:15 PM, John-Mark Gurney wrote: > > > Slawa Olhovchenkov wrote this message on Sun, Mar 29, 2015 at 00:34 +0300: > > > On Sat, Mar 28, 2015 at 01:43:33PM -0700, John-Mark Gurney wrote: > > > > > > In this case may be do range allocation of ID (per-CPU)? > > > For example, allocate 128 ID, not one ID? > > > > Do you mean what to do in the case of an atomic packet? > > > > Per RFC: > > In atomic datagrams, the IPv4 ID field has no meaning; thus, it can > > be set to an arbitrary value, i.e., the requirement for non-repeating > > IDs within the source address/destination address/protocol tuple is > > no longer required for atomic datagrams: > > > > You can just set it to 0, or any value we feel like. > > > > My reading was to give each CPU its own range from which to allocate IDs, > to guarantee that there are no collisions between CPUs. Yes.