mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yunsheng Lin <linyunsheng@huawei.com>
To: Yuval Mintz <yuvalm@mellanox.com>,
	"davem@davemloft.net" <davem@davemloft.net>
Cc: "huangdaode@hisilicon.com" <huangdaode@hisilicon.com>,
	"xuwei5@hisilicon.com" <xuwei5@hisilicon.com>,
	"liguozhu@hisilicon.com" <liguozhu@hisilicon.com>,
	"Yisen.Zhuang@huawei.com" <Yisen.Zhuang@huawei.com>,
	"gabriele.paoloni@huawei.com" <gabriele.paoloni@huawei.com>,
	"john.garry@huawei.com" <john.garry@huawei.com>,
	"linuxarm@huawei.com" <linuxarm@huawei.com>,
	"salil.mehta@huawei.com" <salil.mehta@huawei.com>,
	"lipeng321@huawei.com" <lipeng321@huawei.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 1/2] mqprio: Add a new hardware offload type in mqprio
Date: Fri, 13 Oct 2017 10:12:38 +0800	[thread overview]
Message-ID: <7d1bb860-16c2-3ed6-7f18-d1366ff709d6@huawei.com> (raw)
In-Reply-To: <AM0PR0502MB3683208C0F411F67C70BF6B1BF4B0@AM0PR0502MB3683.eurprd05.prod.outlook.com>

Hi, Yuval

On 2017/10/13 4:10, Yuval Mintz wrote:
>> 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
> 

Will do, Thanks

>> and mqprio may be using the same hardwere offload component and share
> s/hardwere/hardware

Will do, Thanks

> 
>> 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

Will do, Thanks

> 
>> incapable of that it would refuse the offload. User would then have
>> to explicitly request that qdisc offload.
> 
> 
> 

  reply	other threads:[~2017-10-13  2:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12  2:38 [PATCH net-next 0/2] Add mqprio hardware offload support in hns3 driver Yunsheng Lin
2017-10-12  2:38 ` [PATCH net-next 1/2] mqprio: Add a new hardware offload type in mqprio Yunsheng Lin
2017-10-12 20:10   ` Yuval Mintz
2017-10-13  2:12     ` Yunsheng Lin [this message]
2017-10-12  2:38 ` [PATCH net-next 2/2] net: hns3: Add mqprio hardware offload support in hns3 driver Yunsheng Lin
2017-10-12 20:21 ` [PATCH net-next 0/2] " Yuval Mintz
2017-10-13  2:07   ` Yunsheng Lin
2017-10-15  5:14     ` Yuval Mintz
2017-10-15  8:51       ` Yuval Mintz
2017-10-16  1:55         ` Yunsheng Lin
2017-10-16  1:41       ` Yunsheng Lin
2017-10-16  6:25         ` Yuval Mintz
2017-10-16  7:05           ` Yunsheng Lin

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=7d1bb860-16c2-3ed6-7f18-d1366ff709d6@huawei.com \
    --to=linyunsheng@huawei.com \
    --cc=Yisen.Zhuang@huawei.com \
    --cc=davem@davemloft.net \
    --cc=gabriele.paoloni@huawei.com \
    --cc=huangdaode@hisilicon.com \
    --cc=john.garry@huawei.com \
    --cc=liguozhu@hisilicon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=lipeng321@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=salil.mehta@huawei.com \
    --cc=xuwei5@hisilicon.com \
    --cc=yuvalm@mellanox.com \
    /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

all inboxes | Powered by JetHome®