From: "Kadam, Pallavi" <pallavi.kadam@intel.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dev@dpdk.org, thomas@monjalon.net, ranjit.menon@intel.com,
Narcisa.Vasile@microsoft.com, talshn@nvidia.com
Subject: Re: [dpdk-dev] [PATCH] eal/windows: add interrupt functions stub
Date: Mon, 14 Dec 2020 16:38:59 -0800 [thread overview]
Message-ID: <2ff06ee3-d00a-d7a4-019e-10c2fae4fc34@intel.com> (raw)
In-Reply-To: <20201212000741.0344a4e9@sovereign>
Hi Dmitry,
On 12/11/2020 1:07 PM, Dmitry Kozlyuk wrote:
> On Thu, 10 Dec 2020 16:26:07 -0800, Pallavi Kadam wrote:
>> Add some missing interrupt implementations on Windows.
>> Also add respestive functions to export file.
>>
>> Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
>> Signed-off-by: Pallavi Kadam <pallavi.kadam@intel.com>
>> Reviewed-by: Ranjit Menon <ranjit.menon@intel.com>
>> ---
>> lib/librte_eal/rte_eal_exports.def | 11 ++++
>> lib/librte_eal/windows/eal_interrupts.c | 76 +++++++++++++++++++++++++
>> 2 files changed, 87 insertions(+)
>>
>> diff --git a/lib/librte_eal/rte_eal_exports.def b/lib/librte_eal/rte_eal_exports.def
>> index 6a6be1cfa..98a38ed32 100644
>> --- a/lib/librte_eal/rte_eal_exports.def
>> +++ b/lib/librte_eal/rte_eal_exports.def
>> @@ -63,6 +63,17 @@ EXPORTS
>> rte_get_tsc_hz
>> rte_hexdump
>> rte_hypervisor_get
>> + rte_intr_ack
>> + rte_intr_allow_others
>> + rte_intr_callback_register
>> + rte_intr_callback_unregister
>> + rte_intr_cap_multiple
>> + rte_intr_disable
>> + rte_intr_dp_is_en
>> + rte_intr_efd_disable
>> + rte_intr_efd_enable
>> + rte_intr_enable
>> + rte_intr_free_epoll_fd
> Might as well add all remaining interrupt APIs:
>
> rte_intr_callback_unregister_pending
> rte_intr_tls_epfd
Sent out v2 with additional interrupt APIs.
Please let me know if anything is missing.
Thanks,
>
>> rte_intr_rx_ctl
>> rte_lcore_count
>> rte_lcore_has_role
next prev parent reply other threads:[~2020-12-15 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 0:26 Pallavi Kadam
2020-12-11 19:53 ` Narcisa Ana Maria Vasile
2020-12-11 21:07 ` Dmitry Kozlyuk
2020-12-15 0:38 ` Kadam, Pallavi [this message]
2020-12-15 0:26 ` [dpdk-dev] [PATCH v2] " Pallavi Kadam
2020-12-15 22:39 ` Dmitry Kozlyuk
2021-01-05 21:39 ` 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=2ff06ee3-d00a-d7a4-019e-10c2fae4fc34@intel.com \
--to=pallavi.kadam@intel.com \
--cc=Narcisa.Vasile@microsoft.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@nvidia.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).