From: Patrick Mahan <mahan@mahan.org>
To: Joubert Berger <joubertb@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Writing a new driver
Date: Mon, 16 Jun 2014 11:34:40 -0700 [thread overview]
Message-ID: <18573A5E-E333-4644-A15C-3B79357EAAAB@mahan.org> (raw)
In-Reply-To: <CA+ZpPewpBPtGfgp344q9v_V_muPbPLgfNfhy7rfiHTC5ox1XxA@mail.gmail.com>
Joubert,
By all means, look at the existing PMDs. It also helps if you have an existing kernel driver to use/modify (preferably BSD based). That way you can have a baseline to compare against.
At least, that is method I used.
Patrick
> On Jun 13, 2014, at 9:08 AM, Joubert Berger <joubertb@gmail.com> wrote:
>
> I am looking at writing a new driver for DPDK for a NIC that is currently
> not supported. What is the best way to start this? Is the a porting
> guide? Or should I look at existing drivers as examples?
>
> --joubert
prev parent reply other threads:[~2014-06-16 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 16:08 Joubert Berger
2014-06-16 18:34 ` Patrick Mahan [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=18573A5E-E333-4644-A15C-3B79357EAAAB@mahan.org \
--to=mahan@mahan.org \
--cc=dev@dpdk.org \
--cc=joubertb@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).