DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Sujith Sankar (ssujith)" <ssujith@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] PMD for Cisco VIC Ethernet NIC - Request for guidelines for submission
Date: Wed, 28 May 2014 06:05:49 +0000	[thread overview]
Message-ID: <CFAB7A96.19CB4%ssujith@cisco.com> (raw)

Hi all,

We have been working on development of poll-mode driver for Cisco VIC
Ethernet NIC and integration of it with DPDK.  We would like to submit
this poll-mode driver (ENIC PMD) to the DPDK community so that it could be
part of the DPDK tree.

Could someone please provide the guidelines and steps to do this?  As of
now, ENIC PMD is being tested with DPDK 1.6.0r2.  Is it alright to submit
a patch for DPDK 1.6.0r2?

One aspect of ENIC PMD is that it works with VFIO-PCI and not UIO.  Hope
this is acceptable.  The following thread in dpdk-dev influenced this
decision.
http://dpdk.org/ml/archives/dev/2013-July/000373.html

ENIC PMD uses one interrupt per interface and it is used by the NIC for
signalling the driver in case of any error.  Since this does not come in
the fast path, it should be acceptable, isn¹t it?

Please give your suggestions and comments.

Thanks,
-Sujith

             reply	other threads:[~2014-05-28  6:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28  6:05 Sujith Sankar (ssujith) [this message]
2014-05-28  8:52 ` Burakov, Anatoly
2014-05-29  5:07   ` Sujith Sankar (ssujith)
2014-07-09 14:35 [dpdk-dev] [PATCH 0/2] Fixed/Simplified Ring PMD Pablo de Lara
2014-07-09 15:20 ` Neil Horman
2014-07-09 20:07   ` [dpdk-dev] PMD for Cisco VIC Ethernet NIC - Request for guidelines for submission Hobywan Kenoby
2014-07-11  7:46     ` Sujith Sankar (ssujith)
2014-07-11 13:16       ` Hobywan Kenoby
2014-07-21  3:39         ` Sujith Sankar (ssujith)

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=CFAB7A96.19CB4%ssujith@cisco.com \
    --to=ssujith@cisco.com \
    --cc=dev@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).