From: "Miguel Ángel Álvarez" <gotzoncabanes@gmail.com>
To: "Christian Hohnstaedt" <christian@hohnstaedt.de>
Cc: "Krzysztof Halasa" <khc@pm.waw.pl>, netdev@vger.kernel.org
Subject: Re: qmgr for ixp4xx
Date: Wed, 10 Dec 2008 09:48:20 +0100 [thread overview]
Message-ID: <b0438a630812100048v42c4453h353f40c6df494dc4@mail.gmail.com> (raw)
In-Reply-To: <20081209164420.GY16037@mail3.prorata.de>
Hi
On Tue, Dec 9, 2008 at 5:44 PM, Christian Hohnstaedt
<christian@hohnstaedt.de> wrote:
> 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.
>
Thanks for the info, Christian.
Miguel Ángel Álvarez
prev parent reply other threads:[~2008-12-10 8:48 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
2008-12-10 8:48 ` Miguel Ángel Álvarez [this message]
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=b0438a630812100048v42c4453h353f40c6df494dc4@mail.gmail.com \
--to=gotzoncabanes@gmail.com \
--cc=christian@hohnstaedt.de \
--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