[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM0PR0502MB3683208C0F411F67C70BF6B1BF4B0@AM0PR0502MB3683.eurprd05.prod.outlook.com>
Date: Thu, 12 Oct 2017 20:10:28 +0000
From: Yuval Mintz <yuvalm@...lanox.com>
To: Yunsheng Lin <linyunsheng@...wei.com>,
"davem@...emloft.net" <davem@...emloft.net>
CC: "huangdaode@...ilicon.com" <huangdaode@...ilicon.com>,
"xuwei5@...ilicon.com" <xuwei5@...ilicon.com>,
"liguozhu@...ilicon.com" <liguozhu@...ilicon.com>,
"Yisen.Zhuang@...wei.com" <Yisen.Zhuang@...wei.com>,
"gabriele.paoloni@...wei.com" <gabriele.paoloni@...wei.com>,
"john.garry@...wei.com" <john.garry@...wei.com>,
"linuxarm@...wei.com" <linuxarm@...wei.com>,
"yisen.zhuang@...wei.com" <yisen.zhuang@...wei.com>,
"salil.mehta@...wei.com" <salil.mehta@...wei.com>,
"lipeng321@...wei.com" <lipeng321@...wei.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH net-next 1/2] mqprio: Add a new hardware offload type in
mqprio
> When a driver supports both dcb and hardware offloaded mqprio, and
> user is running mqprio and dcb tool concurrently, the configuration
> set by each tool may be conflicted with each other because the dcb
(for second 'each') s/each/the
> and mqprio may be using the same hardwere offload component and share
s/hardwere/hardware
> the tc system in the network stack.
>
> This patch adds a new offload type to indicate that the underlying
> driver offload prio mapping as part of DCB. If the driver would be
'should' offload
> incapable of that it would refuse the offload. User would then have
> to explicitly request that qdisc offload.
Powered by blists - more mailing lists