[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200128235227.3942256-1-vinicius.gomes@intel.com>
Date: Tue, 28 Jan 2020 15:52:24 -0800
From: Vinicius Costa Gomes <vinicius.gomes@...el.com>
To: netdev@...r.kernel.org
Cc: Vinicius Costa Gomes <vinicius.gomes@...el.com>, jhs@...atatu.com,
xiyou.wangcong@...il.com, jiri@...nulli.us, davem@...emloft.net,
vladimir.oltean@....com, po.liu@....com
Subject: [PATCH net v2 0/3] taprio: Some fixes
Hi,
Changes from v1:
- Fixed ignoring the 'flags' argument when adding a new
instance (Vladimir Oltean);
- Changed the order of commits;
Updated cover letter:
Some fixes for taprio, mostly (2/3 and 3/3) related to the 'flags'
argument:
Patch 1/3: Reported by Po Liu, is more of a improvement of usability for
drivers implementing offloading features, now they can rely on the
value of dev->num_tc, instead of going through some hops to get this
value.
Patch 2/3: Use 'q->flags' as the source of truth for the offloading
flags.
Patch 3/3: Fixes the issue that changing the flags during runtime was
still allowed (with bad results). The solution was to initialize
'q->flags' with an invalid value.
Cheers,
--
Vinicius
Vinicius Costa Gomes (3):
taprio: Fix enabling offload with wrong number of traffic classes
taprio: Allow users not to specify "flags" when changing schedules
taprio: Fix still allowing changing the flags during runtime
net/sched/sch_taprio.c | 87 ++++++++++++++++++++++++++----------------
1 file changed, 54 insertions(+), 33 deletions(-)
--
2.25.0
Powered by blists - more mailing lists