public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Hohnstaedt <christian@hohnstaedt.de>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Miguel ?ngel ?lvarez <gotzoncabanes@gmail.com>, netdev@vger.kernel.org
Subject: Re: qmgr for ixp4xx
Date: Tue, 9 Dec 2008 17:44:20 +0100	[thread overview]
Message-ID: <20081209164420.GY16037@mail3.prorata.de> (raw)
In-Reply-To: <m3fxl2jx0v.fsf@maximus.localdomain>

On Fri, Dec 05, 2008 at 07:29:36PM +0100, Krzysztof Halasa wrote:
> "Miguel ?ngel ?lvarez" <gotzoncabanes@gmail.com> writes:
> 
> > I will check for the 64-queue support patch (thanks Karl). However, if
> > I am not sure they are required. I mean...
> > - HSS0 uses queues 12-22.
> > - HSS1 uses queues 0-10.
> > - That leaves us 10 queues free, doesn't it? Couldn't we use queue 11
> > for eth txreadyq, 23-26 for HSS0 txreadyq, 27-30 for HSS1 txreadyq and
> > 31 for crypto code (which I do not know?)
> 
> Ethernet needs 3 queues per port + 1 (465 CPUs can have 3 Ethernet
> ports), the crypto code probably needs several ones.

Crypto needs 2 queues: 29 and 30.
The numbers are fixed in the microcode, I think.

Christian


  parent reply	other threads:[~2008-12-09 16:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 18:44 qmgr for ixp4xx Miguel Ángel Álvarez
2008-12-04 21:06 ` Krzysztof Halasa
2008-12-05  8:51   ` Miguel Ángel Álvarez
2008-12-05 16:03     ` Krzysztof Halasa
2008-12-05 16:59       ` Miguel Ángel Álvarez
2008-12-05 18:29         ` Krzysztof Halasa
2008-12-09  9:48           ` Miguel Ángel Álvarez
2008-12-10  0:56             ` Krzysztof Halasa
2008-12-10  9:04               ` Miguel Ángel Álvarez
2008-12-10 16:32                 ` Miguel Ángel Álvarez
2008-12-09 16:44           ` Christian Hohnstaedt [this message]
2008-12-10  8:48             ` Miguel Ángel Álvarez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081209164420.GY16037@mail3.prorata.de \
    --to=christian@hohnstaedt.de \
    --cc=gotzoncabanes@gmail.com \
    --cc=khc@pm.waw.pl \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox