All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Kantee <pooka-X3B1VOXEql0@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: plumbing say test-pmd for non-Intel NICs(drivers)
Date: Wed, 29 May 2013 16:23:07 +0200	[thread overview]
Message-ID: <51A60F4B.4090908@iki.fi> (raw)
In-Reply-To: <CAMXF-eUzCp0hJN62RezdJv==Fs9jWf4ywT5CXKgjLQhXip9e0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 29.05.2013 10:27, somnath kotur wrote:
> Hi,
>    Pls pardon me if this has been asked/addressed in another thread. Just
> wanted to know what i need to do if i wanted to plumb my non-Intel 10G NIC
> into the DPDK , For instance just into the test-pmd framework would also be
> fine ?
> Any pointers /tips welcome?

Hi,

In short, you'd have to write/port a driver for the NIC.  I very 
recently did this for the purpose of testing DPDK in a virtual machine 
(*).  That said, I got off easy since almost all of the driver code 
already existed, and I only had to make minor edits and redo the parts 
involved with DMA descriptors.

If you have an understanding of how NIC drivers work, it will take a 
varying amount of effort depending on the amount of driver you can 
copypaste from other sources.  However, there's no way around having to 
know how drivers work.

   - antti

*) https://github.com/anttikantee/dpdk-wm

  parent reply	other threads:[~2013-05-29 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  8:27 plumbing say test-pmd for non-Intel NICs(drivers) somnath kotur
     [not found] ` <CAMXF-eUzCp0hJN62RezdJv==Fs9jWf4ywT5CXKgjLQhXip9e0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-29 14:23   ` Antti Kantee [this message]
     [not found]     ` <51A60F4B.4090908-X3B1VOXEql0@public.gmane.org>
2013-05-29 15:07       ` Stephen Hemminger
2013-05-29 15:24   ` Thomas Monjalon

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=51A60F4B.4090908@iki.fi \
    --to=pooka-x3b1voxeql0@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.