From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Netala, Sameera" <Sameera.Netala@cavium.com>,
"users@dpdk.org" <users@dpdk.org>, DPDK <dev@dpdk.org>
Subject: Re: [dpdk-users] Is PF-only driver allowed to upstream into dpdk?
Date: Mon, 13 Feb 2017 10:05:36 +0000 [thread overview]
Message-ID: <797b7a41-b292-5720-2535-6e78e2df7af3@intel.com> (raw)
In-Reply-To: <DM3PR07MB22838BAE47C5E8E7DD63299AE1590@DM3PR07MB2283.namprd07.prod.outlook.com>
On 2/13/2017 9:43 AM, Netala, Sameera wrote:
> Hi,
Hi Sameera,
>
> I am currently working on a non-nic mode user space PCI driver which processes custom packets from OCTEON 7xxx processor. As per the requirements, DPDK is the best way to achieve this.
Can you please give more information about hardware? Is this an offload
engine?
>
> Though I have seen few designs and sources that talk about dpdk pf drivers, I am interested to know if such a driver with pf-only support and which doesn't involve virtual functions will be allowed to upstream into DPDK sources.
There is no problem with PF only drivers, and there are already samples
of it in the project.
As long as driver is open source and for data path, it is good for
upstream. Please feel free to upstream your driver when it is ready.
The discussion about DPDK PF drivers was about if DPDK PF driver should
be in control path or not, this is high level project scope discussion.
Thanks,
ferruh
>
> Thanks,
> Sameera
>
next prev parent reply other threads:[~2017-02-13 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B472A594F5DC19CF.a8c91167-e9c4-4298-b7ca-05352d2b7997@mail.outlook.com>
2017-02-13 9:43 ` Netala, Sameera
2017-02-13 10:05 ` Ferruh Yigit [this message]
[not found] <18142536.l3p9GNq4yZ@xps13>
2017-02-13 22:14 ` Vincent JARDIN
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=797b7a41-b292-5720-2535-6e78e2df7af3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Sameera.Netala@cavium.com \
--cc=dev@dpdk.org \
--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).