From: "Wiles, Keith" <keith.wiles@intel.com>
To: Lin XU <lxu@astri.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] proposal: raw packet send and receive API for PMD driver
Date: Wed, 27 May 2015 14:50:48 +0000 [thread overview]
Message-ID: <D18B41D3.20FDE%keith.wiles@intel.com> (raw)
On 5/26/15, 11:18 PM, "Lin XU" <lxu@astri.org> wrote:
>I think it is very important to decouple PMD driver with DPDK framework.
> (1) Currently, the rte_mbuf struct is too simple and hard to support
>complex application such as IPSEC, flow control etc. This key struct
>should be extendable to support customer defined management header and
>hardware offloading feature.
I was wondering if adding something like M_EXT support for external
storage to DPDK MBUF would be more reasonable.
IMO decoupling PMDs from DPDK will possible impact performance and I would
prefer not to let this happen. The drivers are written for performance,
but they did start out as normal FreeBSD/Linux drivers. Most of the core
code to the Intel drivers are shared between other systems.
> (2) To support more NICs.
>So, I thinks it time to add new API for PMD(a no radical way), and
>developer can add initial callback function in PMD for various upper
>layer protocol procedures.
We have one callback now I think, but what callbacks do you need?
The only callback I can think of is for a stack to know when it can
release its hold on the data as it has been transmitted for retry needs.
>
>
next reply other threads:[~2015-05-27 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 14:50 Wiles, Keith [this message]
2015-05-27 15:30 ` Venkatesan, Venky
-- strict thread matches above, loose matches on Subject: below --
2015-05-27 4:18 Lin XU
2015-05-14 0:26 Guojiachun
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=D18B41D3.20FDE%keith.wiles@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=lxu@astri.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).