From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Jeff Guo <jia.guo@intel.com>, <stephen@networkplumber.org>,
<bruce.richardson@intel.com>, <ferruh.yigit@intel.com>,
<konstantin.ananyev@intel.com>, <gaetan.rivet@6wind.com>,
<jingjing.wu@intel.com>, <thomas@monjalon.net>,
<motih@mellanox.com>, <matan@mellanox.com>,
<harry.van.haaren@intel.com>, <qi.z.zhang@intel.com>,
<shaopeng.he@intel.com>, <bernard.iremonger@intel.com>,
<anatoly.burakov@intel.com>
Cc: <jblunck@infradead.org>, <shreyansh.jain@nxp.com>, <dev@dpdk.org>,
<helin.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/4] eal: modify device event callback process func
Date: Tue, 2 Oct 2018 09:53:20 +0300 [thread overview]
Message-ID: <df109d86-0682-dfca-61c5-99780fd9533a@solarflare.com> (raw)
In-Reply-To: <0b707332-aedc-36b6-d7cb-ac1fd69d9364@intel.com>
On 10/2/18 7:45 AM, Jeff Guo wrote:
> andrew,
>
> On 10/1/2018 5:46 PM, Andrew Rybchenko wrote:
>> On 9/30/18 5:16 PM, Jeff Guo wrote:
>>> This patch modify the device event callback process function name to be
>>> more explicit, change the variable to be const and exposure the API out
>>> from private eal. The bus drivers and eal device would directly use
>>> this
>>> API to process device event callback.
>>
>> Sorry, but from the description it is unclear what has changed to
>> make it necessary.
>>
>
> the reason is that not only eal device help will use the callback, but
> also vfio bus will use
>
> the callback to handle hot-unplug. So exposure these API to let vfio
> call it. I will add detail
>
> more at next version if need.
Yes, it would be good. Thanks.
>
>
>>> Signed-off-by: Jeff Guo<jia.guo@intel.com>
>>> ---
>>> v2->v1:
>>> change the rte_dev_event_callback_prcess from internal to external api
>>> for bus or app usage.
>>> ---
>>> app/test-pmd/testpmd.c | 4 ++--
>>> lib/librte_eal/bsdapp/eal/eal_dev.c | 8 ++++++++
>>> lib/librte_eal/common/eal_common_dev.c | 5 +++--
>>> lib/librte_eal/common/eal_private.h | 12 ------------
>>> lib/librte_eal/common/include/rte_dev.h | 18 +++++++++++++++++-
>>> lib/librte_eal/linuxapp/eal/eal_dev.c | 2 +-
>>> lib/librte_eal/rte_eal_version.map | 1 +
>>> 7 files changed, 32 insertions(+), 18 deletions(-)
>>>
>>> diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c
>>> index bfef483..1313100 100644
>>> --- a/app/test-pmd/testpmd.c
>>> +++ b/app/test-pmd/testpmd.c
>>> @@ -431,7 +431,7 @@ static void check_all_ports_link_status(uint32_t
>>> port_mask);
>>> static int eth_event_callback(portid_t port_id,
>>> enum rte_eth_event_type type,
>>> void *param, void *ret_param);
>>> -static void eth_dev_event_callback(char *device_name,
>>> +static void eth_dev_event_callback(const char *device_name,
>>> enum rte_dev_event_type type,
>>> void *param);
>>> static int eth_dev_event_callback_register(void);
>>> @@ -2249,7 +2249,7 @@ eth_event_callback(portid_t port_id, enum
>>> rte_eth_event_type type, void *param,
>>> /* This function is used by the interrupt thread */
>>> static void
>>> -eth_dev_event_callback(char *device_name, enum rte_dev_event_type
>>> type,
>>> +eth_dev_event_callback(const char *device_name, enum
>>> rte_dev_event_type type,
>>> __rte_unused void *arg)
>>> {
>>> uint16_t port_id;
>>> diff --git a/lib/librte_eal/bsdapp/eal/eal_dev.c
>>> b/lib/librte_eal/bsdapp/eal/eal_dev.c
>>> index ae1c558..374e737 100644
>>> --- a/lib/librte_eal/bsdapp/eal/eal_dev.c
>>> +++ b/lib/librte_eal/bsdapp/eal/eal_dev.c
>>> @@ -33,3 +33,11 @@ rte_dev_hotplug_handle_disable(void)
>>> RTE_LOG(ERR, EAL, "Device event is not supported for FreeBSD\n");
>>> return -1;
>>> }
>>> +
>>> +void __rte_experimental
>>> +rte_dev_event_callback_process(const char *device_name,
>>> + enum rte_dev_event_type event)
>>> +{
>>> + RTE_LOG(ERR, EAL, "Device event callback process is not
>>> supported "
>>> + "for FreeBSD\n");
>>
>> Consider to avoid split of log message to simplify search using grep.
>>
>
> i think i got your point, but the 80 limitation a line and the
> clearly meaning of the log should be the 1 prior to be considerate,
>
> right? It should be considerate but it is inevitable.
It is OK to have line longer than 80 symbols in this case. As far as I
know checkpatches.sh accepts it and does not generate any errors/warnings.
>>> +}
>>> diff --git a/lib/librte_eal/common/eal_common_dev.c
>>> b/lib/librte_eal/common/eal_common_dev.c
>>> index 678dbca..2d610a4 100644
>>> --- a/lib/librte_eal/common/eal_common_dev.c
>>> +++ b/lib/librte_eal/common/eal_common_dev.c
>>> @@ -342,8 +342,9 @@ rte_dev_event_callback_unregister(const char
>>> *device_name,
>>> return ret;
>>> }
>>> -void
>>> -dev_callback_process(char *device_name, enum rte_dev_event_type event)
>>> +void __rte_experimental
>>> +rte_dev_event_callback_process(const char *device_name,
>>> + enum rte_dev_event_type event)
>>> {
>>> struct dev_event_callback *cb_lst;
>>> diff --git a/lib/librte_eal/common/eal_private.h
>>> b/lib/librte_eal/common/eal_private.h
>>> index 637f20d..47e8a33 100644
>>> --- a/lib/librte_eal/common/eal_private.h
>>> +++ b/lib/librte_eal/common/eal_private.h
>>> @@ -259,18 +259,6 @@ struct rte_bus
>>> *rte_bus_find_by_device_name(const char *str);
>>> int rte_mp_channel_init(void);
>>> /**
>>> - * Internal Executes all the user application registered callbacks for
>>> - * the specific device. It is for DPDK internal user only. User
>>> - * application should not call it directly.
>>> - *
>>> - * @param device_name
>>> - * The device name.
>>> - * @param event
>>> - * the device event type.
>>> - */
>>> -void dev_callback_process(char *device_name, enum
>>> rte_dev_event_type event);
>>> -
>>> -/**
>>> * @internal
>>> * Parse a device string and store its information in an
>>> * rte_devargs structure.
>>> diff --git a/lib/librte_eal/common/include/rte_dev.h
>>> b/lib/librte_eal/common/include/rte_dev.h
>>> index ff580a0..58fab43 100644
>>> --- a/lib/librte_eal/common/include/rte_dev.h
>>> +++ b/lib/librte_eal/common/include/rte_dev.h
>>> @@ -39,7 +39,7 @@ struct rte_dev_event {
>>> char *devname; /**< device name */
>>> };
>>> -typedef void (*rte_dev_event_cb_fn)(char *device_name,
>>> +typedef void (*rte_dev_event_cb_fn)(const char *device_name,
>>> enum rte_dev_event_type event,
>>> void *cb_arg);
>>> @@ -438,6 +438,22 @@ rte_dev_event_callback_unregister(const char
>>> *device_name,
>>> * @warning
>>> * @b EXPERIMENTAL: this API may change without prior notice
>>> *
>>> + * Executes all the user application registered callbacks for
>>> + * the specific device.
>>> + *
>>> + * @param device_name
>>> + * The device name.
>>> + * @param event
>>> + * the device event type.
>>> + */
>>> +void __rte_experimental
>>> +rte_dev_event_callback_process(const char *device_name,
>>> + enum rte_dev_event_type event);
>>> +
>>> +/**
>>> + * @warning
>>> + * @b EXPERIMENTAL: this API may change without prior notice
>>> + *
>>> * Start the device event monitoring.
>>> *
>>> * @return
>>> diff --git a/lib/librte_eal/linuxapp/eal/eal_dev.c
>>> b/lib/librte_eal/linuxapp/eal/eal_dev.c
>>> index 9f9e1cf..01e3a04 100644
>>> --- a/lib/librte_eal/linuxapp/eal/eal_dev.c
>>> +++ b/lib/librte_eal/linuxapp/eal/eal_dev.c
>>> @@ -271,7 +271,7 @@ dev_uev_handler(__rte_unused void *param)
>>> return;
>>> }
>>> }
>>> - dev_callback_process(uevent.devname, uevent.type);
>>> + rte_dev_event_callback_process(uevent.devname, uevent.type);
>>> }
>>> }
>>> diff --git a/lib/librte_eal/rte_eal_version.map
>>> b/lib/librte_eal/rte_eal_version.map
>>> index a3255aa..b96da50 100644
>>> --- a/lib/librte_eal/rte_eal_version.map
>>> +++ b/lib/librte_eal/rte_eal_version.map
>>> @@ -277,6 +277,7 @@ EXPERIMENTAL {
>>> rte_class_register;
>>> rte_class_unregister;
>>> rte_ctrl_thread_create;
>>> + rte_dev_event_callback_process;
>>> rte_dev_event_callback_register;
>>> rte_dev_event_callback_unregister;
>>> rte_dev_event_monitor_start;
>>
next prev parent reply other threads:[~2018-10-02 6:54 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 10:51 [dpdk-dev] [PATCH v1 0/5] Enable hotplug in vfio Jeff Guo
2018-08-17 10:51 ` [dpdk-dev] [PATCH v1 1/5] eal: add a new req notifier to eal interrupt Jeff Guo
2018-08-17 10:51 ` [dpdk-dev] [PATCH v1 2/5] eal: add a new req event to device event Jeff Guo
2018-08-20 10:37 ` Andrew Rybchenko
2018-08-21 6:56 ` Jeff Guo
2018-08-21 7:20 ` Andrew Rybchenko
2018-08-21 7:37 ` Jeff Guo
2018-08-17 10:51 ` [dpdk-dev] [PATCH v1 3/5] eal: modify device event callback process func Jeff Guo
2018-09-26 12:20 ` Burakov, Anatoly
2018-09-30 10:30 ` Jeff Guo
2018-09-26 12:20 ` Burakov, Anatoly
2018-09-30 10:31 ` Jeff Guo
2018-08-17 10:51 ` [dpdk-dev] [PATCH v1 4/5] pci: add req handler field to generic pci device Jeff Guo
2018-09-26 12:22 ` Burakov, Anatoly
2018-09-29 6:15 ` Jeff Guo
2018-10-01 7:51 ` Burakov, Anatoly
2018-08-17 10:51 ` [dpdk-dev] [PATCH v1 5/5] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-09-26 12:28 ` Burakov, Anatoly
2018-09-29 5:51 ` Jeff Guo
2018-08-20 9:15 ` [dpdk-dev] [PATCH v1 0/5] Enable hotplug in vfio Gaëtan Rivet
2018-08-21 6:45 ` Jeff Guo
2018-08-21 8:17 ` Gaëtan Rivet
2018-09-30 14:16 ` [dpdk-dev] [PATCH v2 0/4] " Jeff Guo
2018-09-30 14:16 ` [dpdk-dev] [PATCH v2 1/4] eal: add a new req notifier to eal interrupt Jeff Guo
2018-10-01 9:46 ` Andrew Rybchenko
2018-10-02 4:30 ` Jeff Guo
2018-10-02 6:51 ` Andrew Rybchenko
2018-09-30 14:16 ` [dpdk-dev] [PATCH v2 2/4] eal: modify device event callback process func Jeff Guo
2018-10-01 9:46 ` Andrew Rybchenko
2018-10-02 4:45 ` Jeff Guo
2018-10-02 6:53 ` Andrew Rybchenko [this message]
2018-09-30 14:16 ` [dpdk-dev] [PATCH v2 3/4] pci: add req handler field to generic pci device Jeff Guo
2018-10-01 9:46 ` Andrew Rybchenko
2018-10-02 6:32 ` Jeff Guo
2018-09-30 14:16 ` [dpdk-dev] [PATCH v2 4/4] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-10-01 9:47 ` Andrew Rybchenko
2018-10-02 5:42 ` Jeff Guo
2018-10-02 12:42 ` [dpdk-dev] [PATCH v2 0/4] Enable hotplug in vfio Jeff Guo
2018-10-02 12:42 ` [dpdk-dev] [PATCH v2 1/4] eal: add a new req notifier to eal interrupt Jeff Guo
2018-10-02 12:42 ` [dpdk-dev] [PATCH v2 2/4] eal: modify device event callback process func Jeff Guo
2018-10-02 12:42 ` [dpdk-dev] [PATCH v2 3/4] pci: add req handler field to generic pci device Jeff Guo
2018-10-02 12:42 ` [dpdk-dev] [PATCH v2 4/4] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-10-02 12:44 ` [dpdk-dev] [PATCH v3 0/4] Enable hotplug in vfio Jeff Guo
2018-10-02 12:44 ` [dpdk-dev] [PATCH v3 1/4] eal: add a new req notifier to eal interrupt Jeff Guo
2018-10-02 12:45 ` [dpdk-dev] [PATCH v3 2/4] eal: modify device event callback process func Jeff Guo
2018-10-02 12:45 ` [dpdk-dev] [PATCH v3 3/4] pci: add req handler field to generic pci device Jeff Guo
2018-10-02 12:45 ` [dpdk-dev] [PATCH v3 4/4] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-10-02 12:58 ` [dpdk-dev] [PATCH v3 0/4] Enable hotplug in vfio Jeff Guo
2018-10-02 12:58 ` [dpdk-dev] [PATCH v3 1/4] eal: add a new req notifier to eal interrupt Jeff Guo
2018-10-02 12:58 ` [dpdk-dev] [PATCH v3 2/4] eal: modify device event callback process func Jeff Guo
2018-10-02 12:58 ` [dpdk-dev] [PATCH v3 3/4] pci: add req handler field to generic pci device Jeff Guo
2018-10-02 12:58 ` [dpdk-dev] [PATCH v3 4/4] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-10-02 14:15 ` Burakov, Anatoly
2018-10-04 5:05 ` Jeff Guo
2018-10-04 6:44 ` [dpdk-dev] [PATCH v4 0/4] Enable hotplug in vfio Jeff Guo
2018-10-04 6:44 ` [dpdk-dev] [PATCH v4 1/4] eal: add a new req notifier to eal interrupt Jeff Guo
2018-10-04 6:44 ` [dpdk-dev] [PATCH v4 2/4] eal: modify device event callback process func Jeff Guo
2018-10-04 6:44 ` [dpdk-dev] [PATCH v4 3/4] pci: add req handler field to generic pci device Jeff Guo
2018-10-15 9:12 ` Thomas Monjalon
2018-10-15 10:01 ` Thomas Monjalon
2018-10-04 6:44 ` [dpdk-dev] [PATCH v4 4/4] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-10-04 9:11 ` [dpdk-dev] [PATCH v4 0/4] Enable hotplug in vfio Burakov, Anatoly
2018-10-15 21:47 ` Thomas Monjalon
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=df109d86-0682-dfca-61c5-99780fd9533a@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=anatoly.burakov@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gaetan.rivet@6wind.com \
--cc=harry.van.haaren@intel.com \
--cc=helin.zhang@intel.com \
--cc=jblunck@infradead.org \
--cc=jia.guo@intel.com \
--cc=jingjing.wu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=matan@mellanox.com \
--cc=motih@mellanox.com \
--cc=qi.z.zhang@intel.com \
--cc=shaopeng.he@intel.com \
--cc=shreyansh.jain@nxp.com \
--cc=stephen@networkplumber.org \
--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).