From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH] Bound TSO defer time (resend) Date: Wed, 18 Oct 2006 17:37:36 +0200 Message-ID: <200610181737.36135.ak@suse.de> References: <20061016202035.6d55b96e@localhost.localdomain> <45345999.4000300@psc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Stephen Hemminger , netdev@vger.kernel.org Return-path: Received: from mx2.suse.de ([195.135.220.15]:3008 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S1161167AbWJRPhm (ORCPT ); Wed, 18 Oct 2006 11:37:42 -0400 To: John Heffner In-Reply-To: <45345999.4000300@psc.edu> Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Tuesday 17 October 2006 06:18, John Heffner wrote: > Stephen Hemminger wrote: > > On Mon, 16 Oct 2006 20:53:20 -0400 (EDT) > > John Heffner wrote: > > >> This patch limits the amount of time you will defer sending a TSO segment > >> to less than two clock ticks, or the time between two acks, whichever is > >> longer. > > > > > Okay, but doing any timing on clock ticks makes the behavior dependent > > on the value of HZ which doesn't seem desirable. Should this be based > > on RTT or a real-time values? > > It would be nice to use a high res clock so you don't depend on HZ, but > this is still expensive on most SMP arch's as I understand it. You can always use xtime. It doesn't have better solution than jiffies though, but it gives you real time. Drawback is that there is some work towards tickless kernels and with that xtime will be more expensive again. But hopefully not by that much. -Andi