From: David Miller <davem@davemloft.net>
To: john.fastabend@gmail.com
Cc: intel-wired-lan@lists.osuosl.org, jeffrey.t.kirsher@intel.com,
netdev@vger.kernel.org
Subject: Re: [net-next PATCH] net: relax setup_tc ndo op handle restriction
Date: Thu, 03 Mar 2016 16:25:46 -0500 (EST) [thread overview]
Message-ID: <20160303.162546.1789026863325812592.davem@davemloft.net> (raw)
In-Reply-To: <20160229192613.24163.31830.stgit@john-Precision-Tower-5810>
From: John Fastabend <john.fastabend@gmail.com>
Date: Mon, 29 Feb 2016 11:26:13 -0800
> I added this check in setup_tc to multiple drivers,
>
> if (handle != TC_H_ROOT || tc->type != TC_SETUP_MQPRIO)
>
> Unfortunately restricting to TC_H_ROOT like this breaks the old
> instantiation of mqprio to setup a hardware qdisc. This patch
> relaxes the test to only check the type to make it equivalent
> to the check before I broke it. With this the old instantiation
> continues to work.
>
> A good smoke test is to setup mqprio with,
>
> # tc qdisc add dev eth4 root mqprio num_tc 8 \
> map 0 1 2 3 4 5 6 7 \
> queues 0@0 1@1 2@2 3@3 4@4 5@5 6@6 7@7
>
> Fixes: e4c6734eaab9 ("net: rework ndo tc op to consume additional qdisc handle paramete")
> Reported-by: Singh Krishneil <krishneil.k.singh@intel.com>
> Reported-by: Jake Keller <jacob.e.keller@intel.com>
...
> Signed-off-by: John Fastabend <john.r.fastabend@intel.com>
Applied, thanks John.
prev parent reply other threads:[~2016-03-03 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 19:26 [net-next PATCH] net: relax setup_tc ndo op handle restriction John Fastabend
2016-03-02 2:09 ` [Intel-wired-lan] " Allan, Bruce W
2016-03-03 21:25 ` David Miller [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=20160303.162546.1789026863325812592.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.fastabend@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox