From mboxrd@z Thu Jan 1 00:00:00 1970 From: Evgeniy Polyakov Subject: Re: [patch 1/4] - Potential performance bottleneck for Linxu TCP Date: Fri, 1 Dec 2006 12:53:07 +0300 Message-ID: <20061201095306.GA21232@2ka.mipt.ru> References: <20061130095232.GA8990@2ka.mipt.ru> <456EAD6E.6040709@yahoo.com.au> <20061130102205.GA20654@2ka.mipt.ru> <20061130.121443.116355312.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Cc: nickpiggin@yahoo.com.au, mingo@elte.hu, wenji@fnal.gov, akpm@osdl.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: To: David Miller Content-Disposition: inline In-Reply-To: <20061130.121443.116355312.davem@davemloft.net> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Nov 30, 2006 at 12:14:43PM -0800, David Miller (davem@davemloft.net) wrote: > > It steals timeslices from other processes to complete tcp_recvmsg() > > task, and only when it does it for too long, it will be preempted. > > Processing backlog queue on behalf of need_resched() will break > > fairness too - processing itself can take a lot of time, so process > > can be scheduled away in that part too. > > Yes, at this point I agree with this analysis. > > Currently I am therefore advocating some way to allow > full input packet handling even amidst tcp_recvmsg() > processing. Isn't it a step in direction of full tcp processing bound to process context? :) -- Evgeniy Polyakov