From: Stephen Hemminger <stephen@networkplumber.org>
To: Ken Cox <kenstir@gmail.com>
Cc: users@dpdk.org
Subject: Re: Porting application from libevent
Date: Wed, 8 Feb 2023 16:00:55 -0800 [thread overview]
Message-ID: <20230208160055.57592913@hermes.local> (raw)
In-Reply-To: <CAJX1j5H=C5DXTGr0ttOW5bG6VyKc+igE0vfkMLDS+RbXRBKiVw@mail.gmail.com>
On Wed, 8 Feb 2023 14:46:19 -0500
Ken Cox <kenstir@gmail.com> wrote:
> I have several server applications based on libevent (
> https://github.com/libevent/libevent) that use high-resolution timers, UDP,
> and TCP sockets. Right now they run on SR-IOV instances and I would like
> to port these to DPDK to get access to bonded interfaces. Any advice?
>
> I read most of the DPDK Programmer's Guide, and looked at the Event Device
> Library, but it is quite low-level and will entail a substantial amount of
> rework.
> I looked at dpdk-ans (https://github.com/ansyun/dpdk-ans), which provides a
> socket API on top of DPDK, but it seems to be not recently maintained.
> I also looked at seastar (https://github.com/scylladb/seastar), which
> provides an event-driven framework on top of DPDK, but it would require a
> complete rewrite from libevent to futures and C++17.
>
> Any advice would be very much appreciated!
>
> --
> -Ken
I have some experience with libevent. It is really mostly a wrapper on
top of file descriptor (epoll) based API. You might be able to do something
with hardware that supports interrupts in DPDK and using rte_epoll().
This would let application wait for packet or other sources. Still would
need to process packets and may or may not get the data you want; then go
back to sleep only if idle. Kind of like the Linux NAPI model. There is
an example of using this in l3fwd-power example.
prev parent reply other threads:[~2023-02-09 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 19:46 Ken Cox
2023-02-09 0:00 ` Stephen Hemminger [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=20230208160055.57592913@hermes.local \
--to=stephen@networkplumber.org \
--cc=kenstir@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).