From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Kevin Wilson <wkevils@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Is there any HW requirement for a NIC to use the eventdev API for implementing Rx/Tx?
Date: Mon, 11 Jun 2018 08:00:14 +0530 [thread overview]
Message-ID: <20180611023012.GA1714@jerin> (raw)
In-Reply-To: <CAGXs5wWPOfAwdfzKiBi8jzy8stHDGS-Fwa2jdOjjKvHx+LcxDw@mail.gmail.com>
-----Original Message-----
> Date: Mon, 11 Jun 2018 05:02:01 +0300
> From: Kevin Wilson <wkevils@gmail.com>
> To: dev@dpdk.org, jerin.jacob@caviumnetworks.com
> Subject: Is there any HW requirement for a NIC to use the eventdev API for
> implementing Rx/Tx?
>
> Hi,
> According to what I understand from:
> http://dpdk.org/doc/guides/eventdevs/index.html
>
> only 3 drivers currently use the eventdev API,
> NXP DPAA,NXP DPAA2 and Octeon SSOVF.
There are two more SW drivers too(implementing the same eventdev API).
http://dpdk.org/doc/guides/eventdevs/sw.html
http://dpdk.org/doc/guides/eventdevs/opdl.html
>
> My question is: is there any HW requirements from a NIC
> so that it will use the eventdev API for RX/TX instead
> of the traditional polling mode used by all the other PMD drivers ?
> Or theoretically and practically, one can implement DPDK driver using the
> eventndev API for Rx/Tx for any NIC ?
No HW requirement. For the poll mode ONLY NICs, application can use SW event driver to
enable event mode. The NIC driver(ethdev) completely isolated from
eventdev. One can use eventdev -> ethdev RX adapter to take the events
from NICs and injects to eventdev. Based on the HW capability of
underneath eventdev and/or ethdev PMD, it can choose to do in HW or with
help of a service core, But the application interface is same irrespective
HW or SW or combination of two.
https://dpdk.org/doc/guides/prog_guide/event_ethernet_rx_adapter.html
/Jerin
>
> Regards,
> Kevin
prev parent reply other threads:[~2018-06-11 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 2:02 Kevin Wilson
2018-06-11 2:30 ` Jerin Jacob [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=20180611023012.GA1714@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=wkevils@gmail.com \
/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).