From: Jarek Poplawski <jarkao2@gmail.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
jeff@garzik.org, netdev@vger.kernel.org, davem@davemloft.net,
Alexander Duyck <alexander.h.duyck@intel.com>
Subject: Re: [UPDATED] [NET-NEXT PATCH 1/2] pkt_sched: Add multiqueue scheduler support
Date: Tue, 2 Sep 2008 05:54:11 +0000 [thread overview]
Message-ID: <20080902055411.GA4180@ff.dom.local> (raw)
In-Reply-To: <1220309354.14337.34.camel@ahduyck-laptop>
On Mon, Sep 01, 2008 at 03:49:14PM -0700, Alexander Duyck wrote:
> On Mon, 2008-09-01 at 23:05 +0200, Jarek Poplawski wrote:
>
> > Mostly looks OK to me, but a few (late) doubts below:
>
> Most of your suggestions I agree with, with the following exceptions.
> > ...
> > > +static int multiq_tune(struct Qdisc *sch, struct nlattr *opt)
> > > +{
> > > + struct multiq_sched_data *q = qdisc_priv(sch);
> > > + struct tc_multiq_qopt *qopt;
> > > + struct Qdisc **queues;
> > > + int i;
> > > +
> > > + if (sch->parent != TC_H_ROOT)
> > > + return -EINVAL;
> >
> > Is it necessary?
> >
> I think so. Basically I want to have this qdisc as the root for all
> other qdiscs because the hardware queue decision needs to be made as
> soon as possible in order to avoid any head of line blocking issues.
> This way you don't end up with multiple qdiscs fighting over hardware
> queues.
OK, but I wonder if it's not enough to treat this as a recommendation?
Actually, since dequeuing is under the common lock here, the main
difference seems to be this checking for subqueue_stopped could happen
a bit earlier, but this should be safe (a subqueue can't get another
packets in the meantime). So maybe I miss something but this looks
like blocking safe even when used as prio's leaf.
Thanks,
Jarek P.
next prev parent reply other threads:[~2008-09-02 5:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 7:23 [UPDATED] [NET-NEXT PATCH 1/2] pkt_sched: Add multiqueue scheduler support Jeff Kirsher
2008-08-30 7:24 ` [UPDATED] [NET-NEXT PATCH 2/2] pkt_action: add new action skbedit Jeff Kirsher
2008-09-02 12:27 ` Jarek Poplawski
2008-09-01 21:05 ` [UPDATED] [NET-NEXT PATCH 1/2] pkt_sched: Add multiqueue scheduler support Jarek Poplawski
2008-09-01 22:49 ` Alexander Duyck
2008-09-02 5:54 ` Jarek Poplawski [this message]
2008-09-02 7:52 ` Jarek Poplawski
2008-09-02 17:18 ` Duyck, Alexander H
2008-09-02 20:09 ` Jarek Poplawski
2008-09-02 20:53 ` Alexander Duyck
-- strict thread matches above, loose matches on Subject: below --
2008-08-30 7:21 Jeff Kirsher
2008-09-12 3:11 ` David Miller
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=20080902055411.GA4180@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=jeffrey.t.kirsher@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.