netdev
[Top] [All Lists]

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

To: Alex Aizman <itn780@xxxxxxxxx>
Subject: Re: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics
From: Andi Kleen <ak@xxxxxx>
Date: 31 Mar 2005 13:41:22 +0200
Date: Thu, 31 Mar 2005 13:41:22 +0200
Cc: open-iscsi@xxxxxxxxxxxxxxxx, "'jamal'" <hadi@xxxxxxxxxx>, "'Dmitry Yusupov'" <dmitry_yus@xxxxxxxxx>, "'James Bottomley'" <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>, "'Rik van Riel'" <riel@xxxxxxxxxx>, mpm@xxxxxxxxxxx, michaelc@xxxxxxxxxxx, ksummit-2005-discuss@xxxxxxxxx, "'netdev'" <netdev@xxxxxxxxxxx>
References: <20050330161522.GH32111@g5.random>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Wed, Mar 30, 2005 at 11:28:07AM -0800, Alex Aizman wrote:
> > Andrea Arcangeli wrote: 
> > 
> > All I care about is to assign a mempool ID to the skb (ID 
> > being unique identifier for the tcp connection I don't care 
> > how the implementation is). 
> 
> It makes sense to provide an API for the NIC driver to allocate skb from the
> *right* mempool. This way if I have plenty of hw rings and/or can allow
> myself a luxury to associate 1-to-1 connection and ring, there's a nice and
> clean memory management model. Even NICs that have only few rings could use
> this - for critical (e.g., storage) connections. 

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.

-Andi

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