From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wu, Jingjing" <jingjing.wu@intel.com>,
"Sexton, Rory" <rory.sexton@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Marjanovic, Nemanja" <nemanja.marjanovic@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/i40e: set no drop for traffic class
Date: Thu, 9 Feb 2017 15:34:20 +0000 [thread overview]
Message-ID: <c88e8b4f-a9d3-6602-e975-5acdd5b56b48@intel.com> (raw)
In-Reply-To: <9BB6961774997848B5B42BEC655768F810CD5C15@SHSMSX103.ccr.corp.intel.com>
On 2/7/2017 3:25 PM, Wu, Jingjing wrote:
>
>
>> -----Original Message-----
>> From: Sexton, Rory
>> Sent: Thursday, January 19, 2017 6:38 PM
>> To: Wu, Jingjing <jingjing.wu@intel.com>
>> Cc: dev@dpdk.org; Marjanovic, Nemanja <nemanja.marjanovic@intel.com>
>> Subject: RE: [PATCH v2] net/i40e: set no drop for traffic class
>>
>> Perhaps the best solution is as suggested to set rte_eth_conf.dcb_capability_en
>> = ETH_DCB_PFC_SUPPORT rte_eth_conf.rxmode.mq_mode =
>> ETH_MQ_RX_DCB_FLAG and set rte_eth_dcb_rx_conf.nb_tcs to the number of
>> tc's to apply Using this port configuration will give the same behavior of the
>> patch and it removes the need for an API change.
>>
>> Rory
>>
> Yes, That's what I thought when the v1 patch. So do we still need this patch now?
I guess answer is No.
The patch is marked as "Rejected" in patchwork, please shout if that is
not the case.
Thanks,
ferruh
prev parent reply other threads:[~2017-02-09 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 13:54 [dpdk-dev] [PATCH v1] " Rory Sexton
2016-12-05 8:44 ` Wu, Jingjing
2016-12-09 14:02 ` Sexton, Rory
2016-12-26 8:45 ` Wu, Jingjing
2017-01-16 15:52 ` [dpdk-dev] [PATCH v2] " rory.sexton
2017-01-17 15:09 ` Wu, Jingjing
2017-01-19 10:38 ` Sexton, Rory
2017-02-07 15:25 ` Wu, Jingjing
2017-02-09 15:34 ` Ferruh Yigit [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=c88e8b4f-a9d3-6602-e975-5acdd5b56b48@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=nemanja.marjanovic@intel.com \
--cc=rory.sexton@intel.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;
as well as URLs for NNTP newsgroup(s).