[<prev] [next>] [day] [month] [year] [list]
Message-ID: <b0438a630902030313l1f48bdeasfcca132bf066877c@mail.gmail.com>
Date: Tue, 3 Feb 2009 12:13:21 +0100
From: Miguel Ángel Álvarez <gotzoncabanes@...il.com>
To: Krzysztof Halasa <khc@...waw.pl>,
Karl Hiramoto <karl@...amoto.org>,
linux-arm-kernel <linux-arm-kernel@...ts.arm.linux.org.uk>,
linux-kernel@...r.kernel.org
Subject: IXP4XX: Assign queues
Hi
I have a problem assigning queues to ethernet and HSS. In my system, I
am trying to use both HSS in the NPEA, and ethernet in NPEB and NPEC.
Additionally I am trying to use four HDLC per HSS.
It seems there are fixed some fixed queues, while others can be
changed. I have added a 64 queues patch (not enough queues for all the
devices), and trying not to modify the queues assigned for ethernet in
ixdp425-setup.c
Take a look to the following table (in which I put the changeable
queues between "()").
txreadyq rxqueue txqueue rxfree txdone
hdlc0 (32) 13 14 18 22
hdlc1 (36) 0 5 1 22
hdlc2 (33) 13 15 19 22
hdlc3 (37) 0 6 2 22
hdlc4 (34) 13 16 20 22
hdlc5 (38) 0 7 3 22
hdlc6 (35) 13 17 21 22
hdlc7 (39) 0 8 4 22
rxq txreadyq txqueue rxqueue txdone
eth0 (3) (20) 24 28 31
eth1 (4) (21) 25 27 31
As queues 23 and 26 seem to be reserved for ethernet in NPEA this
result in queues 10, 11, 12, 29 and 30 being free (or reserved for
crypto which I do not use).
So... It seems there is a conflict between queues reserved for rxq and
txreadyq in eth0 and eth1 with queues for rxfree in hdlc4-hdlc7.
As I considered rxq and txreadyq queues in eth0 and eth1 changeable, I
tried assigning them queues 40, 41, 42, and 43 (but the interfaces did
not work anymore). Trying different combinations, I have discovered
that rxq must be bellow 32 (so I have assigned them queues 10 and 11),
while txreadyq can be whatever (40 and 41 in my case).
Am I working in the right direction? If so... Couldn't we agree in a
queue mapping that satisfy all needs so that it must not be changed?
Thanks
Miguel Ángel Álvarez
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists