From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261222AbVFDCPz (ORCPT ); Fri, 3 Jun 2005 22:15:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261223AbVFDCPz (ORCPT ); Fri, 3 Jun 2005 22:15:55 -0400 Received: from smtp206.mail.sc5.yahoo.com ([216.136.129.96]:37514 "HELO smtp206.mail.sc5.yahoo.com") by vger.kernel.org with SMTP id S261222AbVFDCPu (ORCPT ); Fri, 3 Jun 2005 22:15:50 -0400 Message-ID: <42A10ED2.7020205@yahoo.com.au> Date: Sat, 04 Jun 2005 12:15:46 +1000 From: Nick Piggin User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050324 Debian/1.7.6-1 X-Accept-Language: en MIME-Version: 1.0 To: Herbert Xu CC: mbligh@mbligh.org, davem@davemloft.net, jschopp@austin.ibm.com, mel@csn.ul.ie, linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@osdl.org Subject: Re: Avoiding external fragmentation with a placement policy Version 12 References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Herbert Xu wrote: > Nick Piggin wrote: > >>network code. If the latter, that would suggest at least in theory >>it could use noncongiguous physical pages. > > > With Dave's latest super-TSO patch, TCP over loopback will only be > doing order-0 allocations in the common case. UDP and others may > still do large allocations but that logic is all localised in > ip_append_data. > > So if we wanted we could easily remove most large allocations over > the loopback device. I would be very interested to look into that. I would be willing to do benchmarks on a range of machines too if that would be of any use to you. Thanks, Nick -- SUSE Labs, Novell Inc. Send instant messages to your online friends http://au.messenger.yahoo.com