For some reason linux drops all incoming packets which have a source
address in the 0.0.0.0/8 range, although these are valid addresses. The
attached patch fixes this. (It still drops packets coming from 0.0.0.0
since that's a special address.)
Signed-off-by: Amnon Aaronsohn <[EMAIL P
ached. This patch changes PRIO's behavior so
that it attaches a fifo qdisc to all of the N bands.
Passes the tests suggested by jamal.
Thanks,
Amnon
Signed-off-by: Amnon Aaronsohn <[EMAIL PROTECTED]>
--- linux-2.6.14/net/sched/sch_prio.c 2005-10-28 02:02:08.0 +0200
+++ work-
--- jamal <[EMAIL PROTECTED]> wrote:
> You will always point to correctly initialized
> queues with any
> value of skb->priority.
Ok, to put it concretely:
Suppose we have prio configured thus:
tc qdisc add dev eth0 root handle 1: prio bands 4
This qdisc has 4 bands but it uses the default pri
> > So it is an optimization - not a bug then,
> correct?
It's a bug fix that happens to be an optimization :)
> No matter what you set skb->priority to, that gets
> translated
> by prio2band[] which should only point to actually
> initialized
> queues.
That's not correct. If prio_classify() see
--- jamal <[EMAIL PROTECTED]> wrote:
> Did you actually run into some issues that prompted
> you to produce this
> patch? Why would you want to have something not in
> the priomap to
> do any queueing of packets?
I wrote this patch because the qdisc wasn't running
correctly when I used priorities
The PRIO queuing discipline currently initializes only the bands
that appear in the priomap. It should instead initialize all the
configured bands.
Signed-off-by: Amnon Aaronsohn <[EMAIL PROTECTED]>
---
--- linux-2.6.14/net/sched/sch_prio.c 2005-10-28 02:02:08.0 +0200
+++ work-
