From: "Netala, Sameera" <Sameera.Netala@cavium.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Is PF-only driver allowed to upstream into dpdk?
Date: Mon, 13 Feb 2017 09:43:14 +0000 [thread overview]
Message-ID: <DM3PR07MB22838BAE47C5E8E7DD63299AE1590@DM3PR07MB2283.namprd07.prod.outlook.com> (raw)
In-Reply-To: <B472A594F5DC19CF.a8c91167-e9c4-4298-b7ca-05352d2b7997@mail.outlook.com>
Hi,
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.
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.
Thanks,
Sameera
next parent reply other threads:[~2017-02-13 9:43 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 [this message]
2017-02-13 10:05 ` Ferruh Yigit
[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=DM3PR07MB22838BAE47C5E8E7DD63299AE1590@DM3PR07MB2283.namprd07.prod.outlook.com \
--to=sameera.netala@cavium.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).