On Fri, 22 Jul 2011, Rama Puranam wrote:

> Hi,
> 
> I am trying to enable 128 queues per Niantic port. I have four such ports.

do you need 128 tx queues or rx queues or both?
 
> My need to is to have the following configuration.
> 
> FCoE -> Disabled.
> 
> DCA -> Disabled
> 
> FdirMode -> Disabled

if you do this you can't use more than 16 rx queues (rss) - in non-pool 
mode, see below
 
> RSS -> Disabled

if you do this then you can't use more than 1 rx queue because there will 
be nothing to steer the packets to the rx queues - in non-pool mode, see 
below

> VMDq -> Enabled

so you're trying to set up 16 VMQs with 8 queue pairs each? or 8 VMQs 
(pairs) with 16 queues each?

> DCB -> Enabled.

wait, what are you trying to do here? for DCB you get 8 pools of queues 
(one for each priority) with up to 16 queues in each one.

not sure about this, but I thought DCB and VMDq were mutually exclusive.  
we have code in the works to fix co-existence of DCB and RSS, or SR-IOV 
and RSS, but it isn't released yet.  

82599 once in pool mode splits everything up into 8 pieces, 

Basically you're way out past the supported feature set of our drivers.

> Tried to various combinations using the ixgbe driver code, but could not
> enable more than 64 queues per port.

hardware only supports 64 interrupts, but can support 128/128 tx/rx (4 
queues per interrupt)

please describe what you're trying to do, but given the above, I'm pretty 
sure you're beyond our driver's current support.

------------------------------------------------------------------------------
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks & Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to