Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763470AbYCGLzu (ORCPT ); Fri, 7 Mar 2008 06:55:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759082AbYCGLzi (ORCPT ); Fri, 7 Mar 2008 06:55:38 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:44724 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758797AbYCGLzh (ORCPT ); Fri, 7 Mar 2008 06:55:37 -0500 Subject: Re: [PATCH 00/28] Swap over NFS -v16 From: Peter Zijlstra To: Neil Brown Cc: Andrew Morton , Linus Torvalds , linux-kernel@vger.kernel.org, linux-mm@kvack.org, netdev@vger.kernel.org, trond.myklebust@fys.uio.no, Pekka Enberg In-Reply-To: <1204888675.8514.102.camel@twins> References: <20080220144610.548202000@chello.nl> <20080223000620.7fee8ff8.akpm@linux-foundation.org> <18371.43950.150842.429997@notabene.brown> <1204023042.6242.271.camel@lappy> <18372.64081.995262.986841@notabene.brown> <1204099113.6242.353.camel@lappy> <1837 <1204626509.6241.39.camel@lappy> <18384.46967.583615.711455@notabene.brown> <1204888675.8514.102.camel@twins> Content-Type: text/plain Date: Fri, 07 Mar 2008 12:55:31 +0100 Message-Id: <1204890931.8514.107.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.21.92 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1168 Lines: 30 On Fri, 2008-03-07 at 12:17 +0100, Peter Zijlstra wrote: > That would be so if the whole path from RX to socket demux would have > hard-irqs disabled. However I didn't see that. Moreover I think the > whole purpose of the NetPoll interface is to allow some RX queueing to > cut down on softirq overhead. s/NetPoll/NAPI/ More specifically look at net/core/dev.c:netif_rx() It has a input queue per device. > > 2/ If the host is routing network packets, then incoming packets > > might go on an outbound queue. Is this space limited? and > > included in the reserve? > > Not sure, somewhere along the routing code I lost it again. Constructive > input from someone versed in that part of the kernel would be most > welcome. To clarify, I think we just send it on as I saw no reason why that could fail. However the more fancy stuff like engress or QoS might spoil the party, that is where I lost track. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/