From: Stephen Hemminger <stephen@networkplumber.org>
To: Priya Ramanathan <shunmugapriya.ramanathan@gmail.com>
Cc: users@dpdk.org,
Koteswararao Kondepu <koteswararao.kondepu@gmail.com>,
andreaf <andreaf@utdallas.edu>
Subject: Re: Does DPDK supports EPOLL for 10G X550T (ixgbe driver)
Date: Thu, 19 Jan 2023 20:04:15 -0800 [thread overview]
Message-ID: <20230119200415.5a976e90@hermes.local> (raw)
In-Reply-To: <CAMgau3kua4yMD9NJKim6rZB+iyruMb0kdkwfPVAOmVsem60G6w@mail.gmail.com>
On Thu, 19 Jan 2023 16:29:16 -0600
Priya Ramanathan <shunmugapriya.ramanathan@gmail.com> wrote:
> Thank you, for the information.
> I have a UDPDK stack (with DPDK at the physical layer) for UDP
> communication.
>
> I am using VFIO module and binded the 10G X550T NIC to the VFIO module.
> Then I wrote a simple server-client code for UDP communication using the
> UDPDK APIs with DPDK support, which works fine.
> Now, I added the epoll_create, epoll_ctl and epoll_wait commands, and it
> looks like it is not working as expected.
>
> Let me go through the l3fwd example and try to understand it better. If I
> get any questions, I will get back to you. Thank you.
>
> Regards,
> Priya.
There is no file descriptor visible to poll on in DPDK.
You need to use DPDK interrupt mode which is rte_epoll.
Also, if DPDK wakes up in interrupt mode, it might not be a UDP
packet, it could be any type of packet that your stack has to digest
(ARP, ICMP, UDP, etc)
next prev parent reply other threads:[~2023-01-20 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 19:43 Priya Ramanathan
2023-01-19 22:14 ` Stephen Hemminger
2023-01-19 22:29 ` Priya Ramanathan
2023-01-20 4:04 ` Stephen Hemminger [this message]
2023-01-30 17:53 ` Priya Ramanathan
2023-01-30 19:21 ` Priya Ramanathan
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=20230119200415.5a976e90@hermes.local \
--to=stephen@networkplumber.org \
--cc=andreaf@utdallas.edu \
--cc=koteswararao.kondepu@gmail.com \
--cc=shunmugapriya.ramanathan@gmail.com \
--cc=users@dpdk.org \
/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).