From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>,
Yasufumi Ogawa <usufumu@gmail.com>
Cc: x-fn-spp@sl.ntt-tx.co.jp, ferruh.yigit@intel.com, spp@dpdk.org
Subject: Re: [spp] [spp 03539] Re: [PATCH 0/6] Replace deprecated APIs
Date: Tue, 13 Nov 2018 17:22:55 +0900 [thread overview]
Message-ID: <22b6ce74-37df-0fd7-2265-a2206a19b327@lab.ntt.co.jp> (raw)
In-Reply-To: <201811130028.wAD0SYfP013800@ccmail04.silk.ntt-tx.co.jp>
> Hello Yasufumi-san,
>
> Thanks for your comments.
> Please see inline.
>
>>> Hello Yasufumi-san,
>>>
>>> Thanks so much for your comments.
>>>
>>> About your first point, I think the follwing naming may be fit with DPDK
>>> and SPP naming conventions, what do you think?
>>>
>>> attach -> spp_eth_dev_attach
>>> detach -> spp_eth_dev_detach
>> I think you should not use prefix `spp` without if it defines a behaviour of SPP itself. This function is more essential to attach device.
>>
>> For `spp_eth_dev_attach`, You might think similar name from original `rte_eth_dev_attach`, but I think we do not keep the name of deprecated APIs. More simply, how about `dev_attach_by_devargs` instead of?
> I have no problem about naming `dev_attach_by_devargs`.
>
>> For `spp_eth_dev_detach`, I think `dev_detach_by_port_id` is more prefer. Other than the name of the function, I am curious why it takes second argument `name` because it is not used in the function.
> I have no problem about namign `dev_detach_by_port_id`.
> As you say, second argument is NOT used within the function and I will
> remove it from revised version.
>
>> By the way, I am not clear what is the difference between your functions and `rte_eth_dev_attach` defined in `dpdk/lib/librte_ethdev/rte_ethdev.c` exactly. Could you explain about the difference shortly for helping my understanding?
> Basically both of those functions uses `rte_eal_hotplug_add` to hotplug
> device.
Thank you for considering updates.
>
> Difference is described as following:
> `rte_eth_dev_attach` uses global variable named
> eth_dev_last_created_port when retrieving newly created dpdk port while
> my new function uses `rte_eth_dev_get_port_by_name` becauase this function is defined outside
> of dpdk library and can not retrieve global variable within dpdk library.
I've got understand your point. Could you confirm why you avoid to use global variable?
Thanks
> BR,
> Hideyuki Yamashita
> NTT TechnoCross
>
>> Thanks
>>> About your second point, I appologize about my mistake.
>>>
>>> Once I get ack for above new naming of two interfaces from you,
>>> I will revise my patch set including cover-letter and will send
>>> those to mailing list.
>>>
>>> Thanks for your co-opearation!
>>>
>>> BR,
>>> Hideyuki Yamashita
>>> NTT TechnoCorss
>>>
>>>> On 2018/11/07 14:07, x-fn-spp@sl.ntt-tx.co.jp wrote:
>>>>> From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
>>>>>
>>>>> >From DPDK-18.08, the follwing APIs become deprecated and
>>>>> will be deleted in DPDK18.08.
>>>>> - rte_eth_dev_attach()
>>>>> - rte_eth_dev_detach()
>>>>>
>>>>> For rte_eth_dev_attach(), use of rte_eal_hotplug_add() is recommended.
>>>>> For rte_eth_dev_detach(), use of rte_eal_hotplug_remove() is recommended.
>>>>>
>>>>> To follow the above changes, this patch set provides replacement of
>>>>> those APIs.
>>>> Hideyuki,
>>>>
>>>> Thank you for suggesting to update to v18.08!
>>>>
>>>> Could you re-consider the name of function you added by referring conventions of DPDK and SPP? It has almost no means if just `attach` or `detach`. It is preferable to be self explanatory for how your function works.
>>>>
>>>> Commit messages are also required to be revised. Update for the change of function name and modify invalid descriptions for documentation guidelines.
>>>>
>>>> Thanks
>>>>> Signed-off-by: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
>>>>> Signed-off-by: Naoki Takada <takada.naoki@lab.ntt.co.jp>
>>>>>
>>>>> Hideyuki Yamashita (6):
>>>>> shared: addition of attach()
>>>>> spp_nfv: replacement of rte_eth_dev_attach()
>>>>> spp_vf:replacement of rte_eth_dev_attach()
>>>>> shared: addition of detach()
>>>>> spp_nfv: replacement of rte_eth_dev_detach()
>>>>> spp_vm: replacement of rte_eth_dev_detach().
>>>>>
>>>>> src/nfv/nfv.c | 12 ++++-----
>>>>> src/shared/common.c | 64 +++++++++++++++++++++++++++++++++++++++++++++
>>>>> src/shared/common.h | 32 +++++++++++++++++++++++
>>>>> src/vf/spp_vf.c | 4 +--
>>>>> src/vm/main.c | 2 +-
>>>>> 5 files changed, 105 insertions(+), 9 deletions(-)
>>>>>
>>>>
>>>>
>
>
>
>
--
Yasufumi Ogawa
NTT Network Service Systems Labs
next prev parent reply other threads:[~2018-11-13 8:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 5:07 [spp] " x-fn-spp
2018-11-09 3:34 ` Yasufumi Ogawa
2018-11-09 9:22 ` [spp] [spp 03539] " Hideyuki Yamashita
2018-11-12 11:15 ` Yasufumi Ogawa
2018-11-13 0:27 ` Hideyuki Yamashita
2018-11-13 8:22 ` Yasufumi Ogawa [this message]
2018-11-14 0:40 ` Hideyuki Yamashita
2018-11-15 0:16 ` Nakamura Hioryuki
2018-11-15 14:17 ` Yasufumi Ogawa
2018-11-21 6:52 ` [spp] [PATCH v2 " x-fn-spp
2018-11-24 12:57 ` Yasufumi Ogawa
2018-11-28 2:44 ` Yasufumi Ogawa
2018-11-21 6:52 ` [spp] [PATCH v2 1/6] shared: add dev_attach_by_devargs x-fn-spp
2018-11-24 14:54 ` Yasufumi Ogawa
2018-11-26 4:12 ` [spp] [spp 03664] " Hideyuki Yamashita
2018-11-21 6:52 ` [spp] [PATCH v2 2/6] spp_nfv: replace deprecated rte_eth_dev_attach x-fn-spp
2018-11-21 6:52 ` [spp] [PATCH v2 3/6] spp_vf: " x-fn-spp
2018-11-21 6:52 ` [spp] [PATCH v2 4/6] shared: add dev_detach_by_port_id x-fn-spp
2018-11-24 15:02 ` Yasufumi Ogawa
2018-11-21 6:52 ` [spp] [PATCH v2 5/6] spp_nfv: replace deprecated rte_eth_dev_detach x-fn-spp
2018-11-21 6:52 ` [spp] [PATCH v2 6/6] spp_vm: " x-fn-spp
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=22b6ce74-37df-0fd7-2265-a2206a19b327@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
--cc=usufumu@gmail.com \
--cc=x-fn-spp@sl.ntt-tx.co.jp \
--cc=yamashita.hideyuki@po.ntt-tx.co.jp \
/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).