Received: with ECARTIS (v1.0.0; list netdev); Thu, 31 Mar 2005 04:12:43 -0800 (PST) Received: from mx1.redhat.com (mx1.redhat.com [66.187.233.31]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id j2VCCaVF022805 for ; Thu, 31 Mar 2005 04:12:36 -0800 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j2VCCOCO032518; Thu, 31 Mar 2005 07:12:24 -0500 Received: from mail.boston.redhat.com (mail.boston.redhat.com [172.16.76.12]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j2VCCOO06022; Thu, 31 Mar 2005 07:12:24 -0500 Received: from chimarrao.boston.redhat.com (chimarrao.boston.redhat.com [172.16.80.75]) by mail.boston.redhat.com (8.12.8/8.12.8) with ESMTP id j2VCCNv8027322; Thu, 31 Mar 2005 07:12:23 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by chimarrao.boston.redhat.com (8.13.1/8.12.10) with ESMTP id j2VCCMfb002989; Thu, 31 Mar 2005 07:12:22 -0500 Date: Thu, 31 Mar 2005 07:12:22 -0500 (EST) From: Rik van Riel X-X-Sender: riel@chimarrao.boston.redhat.com To: Andi Kleen cc: Alex Aizman , open-iscsi@googlegroups.com, "'jamal'" , "'Dmitry Yusupov'" , "'James Bottomley'" , mpm@selenic.com, michaelc@cs.wisc.edu, ksummit-2005-discuss@thunk.org, "'netdev'" Subject: Re: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics In-Reply-To: <20050331114122.GL24804@muc.de> Message-ID: References: <20050330161522.GH32111@g5.random> <20050331114122.GL24804@muc.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV 0.83/798/Thu Mar 31 01:54:41 2005 on oss.sgi.com X-Virus-Status: Clean X-archive-position: 1091 X-ecartis-version: Ecartis v1.0.0 Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com X-original-sender: riel@redhat.com Precedence: bulk X-list: netdev Content-Length: 592 Lines: 14 On Thu, 31 Mar 2005, Andi Kleen wrote: > It wont work - I can guarantee you that if you add a limit like > "we only support 8 iscsi connections max" then users/customers will raise > hell because it does not fit their networks. What would prevent the iscsi driver from telling the network stack to increase the size of the mempools when additional iscsi connections are configured ? -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan