From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcus Sundberg Subject: Re: [RFC] alternative to conntrack ID Date: Sun, 08 May 2005 00:32:26 +0200 Message-ID: <427D41FA.5080506@ingate.com> References: <424747E3.7000300@eurodev.net> <42502F8D.5030504@trash.net> <4254258E.5000204@eurodev.net> <42627BC4.8070103@trash.net> <20050429080242.GJ9735@sunbeam.de.gnumonks.org> <42789366.20702@ufomechanic.net> <4278B23A.7050406@trash.net> <4278B98E.7090707@ufomechanic.net> <427B8A46.8090006@trash.net> <427D26E7.8060701@ingate.com> <427D3EAF.3020200@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Harald Welte , Netfilter Development Mailinglist , Pablo Neira , Amin Azez Return-path: To: Patrick McHardy In-Reply-To: <427D3EAF.3020200@trash.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org Patrick McHardy wrote: > Marcus Sundberg wrote: > >>You don't even need fast CPUs or networks to risk precision problems >>- think multiple NICs and SMP. > > SMP or multiple NIcs don't matter because at any point in time only > one instance of a connection can exist. The challenge is to have a > unique identifier over time. Yes, having a unique identifier over time was what was being discussed, and I was merely pointing out that with SMP you can get two conntracks with identical timestamps even if you have infinite precision, since two new conntracks can be timestamped simultaneously by different CPUs. //Marcus -- ---------------------------------------+-------------------------- Marcus Sundberg | Firewalls with SIP & NAT Software Developer, Ingate Systems AB | http://www.ingate.com/