From: "Qiu, Michael" <michael.qiu@intel.com>
To: "Xie, Huawei" <huawei.xie@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] lib/librte_pmd_i40e: set vlan filter fix
Date: Mon, 24 Nov 2014 08:32:38 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E60286C99F7A@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B0F2EFEBD@SHSMSX101.ccr.corp.intel.com>
On 11/10/2014 2:42 PM, Xie, Huawei wrote:
>
>> -----Original Message-----
>> From: Zhang, Helin
>> Sent: Sunday, November 09, 2014 10:09 PM
>> To: Xie, Huawei; dev@dpdk.org
>> Subject: RE: [dpdk-dev] [PATCH v2 1/2] lib/librte_pmd_i40e: set vlan filter fix
>>
>>
>>
>>> -----Original Message-----
>>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Huawei Xie
>>> Sent: Monday, November 10, 2014 10:46 AM
>>> To: dev@dpdk.org
>>> Subject: [dpdk-dev] [PATCH v2 1/2] lib/librte_pmd_i40e: set vlan filter fix
>>>
>>> ">> 5" rather than ">> 4"
>>>
>>> Signed-off-by: Huawei Xie <huawei.xie@intel.com>
>>> ---
>>> lib/librte_pmd_i40e/i40e_ethdev.c | 7 ++-----
>>> 1 file changed, 2 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/lib/librte_pmd_i40e/i40e_ethdev.c
>>> b/lib/librte_pmd_i40e/i40e_ethdev.c
>>> index 5074262..c0cf3cf 100644
>>> --- a/lib/librte_pmd_i40e/i40e_ethdev.c
>>> +++ b/lib/librte_pmd_i40e/i40e_ethdev.c
>>> @@ -4048,14 +4048,11 @@ i40e_set_vlan_filter(struct i40e_vsi *vsi, {
>>> uint32_t vid_idx, vid_bit;
>>>
>>> -#define UINT32_BIT_MASK 0x1F
>>> -#define VALID_VLAN_BIT_MASK 0xFFF
>>> /* VFTA is 32-bits size array, each element contains 32 vlan bits, Find the
>>> * element first, then find the bits it belongs to
>>> */
>>> - vid_idx = (uint32_t) ((vlan_id & VALID_VLAN_BIT_MASK) >>
>>> - sizeof(uint32_t));
>>> - vid_bit = (uint32_t) (1 << (vlan_id & UINT32_BIT_MASK));
>>> + vid_idx = (uint32_t) ((vlan_id >> 5 ) & 0x7F);
^^^^^^^^^^^^
No need additional space after '5'
>>> + vid_bit = (uint32_t) (1 << (vlan_id & 0x1F));
>> I don't understand why remove macros and use numeric instead?
> Those macros are wrongly defined. Correct macros are defined in second patch.
Is there any issue to swap your patch order, and use your defined macros
here? That would be much better if no other issue.
Thanks,
Michael
>>> if (on)
>>> vsi->vfta[vid_idx] |= vid_bit;
>>> --
>>> 1.8.1.4
>> Regards,
>> Helin
next prev parent reply other threads:[~2014-11-24 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 2:46 [dpdk-dev] [PATCH v2 0/2] " Huawei Xie
2014-11-10 2:46 ` [dpdk-dev] [PATCH v2 1/2] " Huawei Xie
2014-11-10 5:08 ` Zhang, Helin
2014-11-10 6:42 ` Xie, Huawei
2014-11-24 8:32 ` Qiu, Michael [this message]
2014-11-24 21:41 ` Xie, Huawei
2014-11-10 2:46 ` [dpdk-dev] [PATCH v2 2/2] lib/librte_pmd_i40e: add I40E_VFTA_IDX and I40E_VFTA_BIT macros for VFTA related operation Huawei Xie
2014-11-10 5:08 ` Zhang, Helin
2014-11-10 6:52 ` Xie, Huawei
2014-11-10 8:25 ` [dpdk-dev] [PATCH v2 0/2] lib/librte_pmd_i40e: set vlan filter fix Chen, Jing D
2014-11-21 20:47 ` Xie, Huawei
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=533710CFB86FA344BFBF2D6802E60286C99F7A@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=huawei.xie@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).