From: "Wei Hu (Xavier)" <xavier_huwei@163.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
"Wei Hu (Xavier)" <huwei013@chinasoftinc.com>,
dev@dpdk.org
Cc: Andrew Rybchenko <arybchenko@solarflare.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] ethdev: move non null judgment of ops function pointer ahead
Date: Fri, 17 Jan 2020 11:04:07 +0800 [thread overview]
Message-ID: <3fdd5077-f672-852b-4dd4-3c5ed50de375@163.com> (raw)
In-Reply-To: <c5accdba-bdc9-44a9-ca01-65174696125b@intel.com>
Hi, Ferruh Yigit
On 2020/1/17 5:08, Ferruh Yigit wrote:
> On 1/16/2020 12:27 PM, Wei Hu (Xavier) wrote:
>> From: "Wei Hu (Xavier)" <xavier.huwei@huawei.com>
>>
>> This patch moves the following judgement statement to the first half of
>> the function named rte_eth_dev_set_vlan_offload, so we can avoid changing
>> the content of dev->data->dev_conf.rxmode.offloads even when the pointer
>> named dev->dev_ops->vlan_offload_set is NULL:
>> RTE_FUNC_PTR_OR_ERR_RET(*dev->dev_ops->vlan_offload_set, -ENOTSUP);
>>
>> Signed-off-by: Wei Hu (Xavier) <xavier.huwei@huawei.com>
>> Signed-off-by: Chunsong Feng <fengchunsong@huawei.com>
>> Signed-off-by: Min Wang (Jushui) <wangmin3@huawei.com>
>> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
>> ---
>> lib/librte_ethdev/rte_ethdev.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/librte_ethdev/rte_ethdev.c b/lib/librte_ethdev/rte_ethdev.c
>> index aec2d0f70..21f24cd7f 100644
>> --- a/lib/librte_ethdev/rte_ethdev.c
>> +++ b/lib/librte_ethdev/rte_ethdev.c
>> @@ -3257,6 +3257,7 @@ rte_eth_dev_set_vlan_offload(uint16_t port_id, int offload_mask)
>>
>> RTE_ETH_VALID_PORTID_OR_ERR_RET(port_id, -ENODEV);
>> dev = &rte_eth_devices[port_id];
>> + RTE_FUNC_PTR_OR_ERR_RET(*dev->dev_ops->vlan_offload_set, -ENOTSUP);
>>
>> /* save original values in case of failure */
>> orig_offloads = dev->data->dev_conf.rxmode.offloads;
>> @@ -3307,7 +3308,6 @@ rte_eth_dev_set_vlan_offload(uint16_t port_id, int offload_mask)
>> if (mask == 0)
>> return ret;
>>
>> - RTE_FUNC_PTR_OR_ERR_RET(*dev->dev_ops->vlan_offload_set, -ENOTSUP);
>> ret = (*dev->dev_ops->vlan_offload_set)(dev, mask);
>> if (ret) {
>> /* hit an error restore original values */
>>
>
> I agree this side affect is a defect, thanks for spotting.
>
> Above approach would work, but also I think it was good approach to return
> success (0) when no change at all requested, we are loosing it here.
>
> What do you think,
> - Update a local 'dev_offloads' variable, instead of directly updating the
> device config data
> - if no change requested, "mask == 0", return success
> - if change requested, check the 'vlan_offload_set' dev_ops in this stage
> - assign the local 'dev_offloads' to 'dev->data->dev_conf.rxmode.offloads' and
> call the dev_ops
> - On error recover the 'dev->data->dev_conf.rxmode.offloads' to 'orig_offloads'
>
> This way both side affect can be prevented and API returns success if no change
> requested.
>
I agree your opinion and will send V2.
Thanks
Xavier
prev parent reply other threads:[~2020-01-17 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 12:27 Wei Hu (Xavier)
2020-01-16 21:08 ` Ferruh Yigit
2020-01-17 3:04 ` Wei Hu (Xavier) [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=3fdd5077-f672-852b-4dd4-3c5ed50de375@163.com \
--to=xavier_huwei@163.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=huwei013@chinasoftinc.com \
--cc=thomas@monjalon.net \
/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).