netdev
[Top] [All Lists]

Re: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics

To: Rik van Riel <riel@xxxxxxxxxx>
Subject: Re: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics
From: Andi Kleen <ak@xxxxxx>
Date: 31 Mar 2005 20:59:54 +0200
Date: Thu, 31 Mar 2005 20:59:54 +0200
Cc: Alex Aizman <itn780@xxxxxxxxx>, open-iscsi@xxxxxxxxxxxxxxxx, "'jamal'" <hadi@xxxxxxxxxx>, "'Dmitry Yusupov'" <dmitry_yus@xxxxxxxxx>, "'James Bottomley'" <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>, mpm@xxxxxxxxxxx, michaelc@xxxxxxxxxxx, ksummit-2005-discuss@xxxxxxxxx, "'netdev'" <netdev@xxxxxxxxxxx>
In-reply-to: <Pine.LNX.4.61.0503310711430.21935@chimarrao.boston.redhat.com>
References: <20050330161522.GH32111@g5.random> <20050331114122.GL24804@muc.de> <Pine.LNX.4.61.0503310711430.21935@chimarrao.boston.redhat.com>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Thu, Mar 31, 2005 at 07:12:22AM -0500, Rik van Riel wrote:
> 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 ?

I was talking about the hardware limits for early filtering,
not the size of the mempools.

All hardware I found so far has small limits like this.

-Andi

<Prev in Thread] Current Thread [Next in Thread>