DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Patrick Mahan <mahan@mahan.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Question regarding PMDs
Date: Wed, 31 Jul 2013 14:35:18 -0700	[thread overview]
Message-ID: <20130731143518.7eee47cf@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1486472B-BF17-4A85-887A-806E6DB32480@mahan.org>

On Wed, 31 Jul 2013 14:23:40 -0700
Patrick Mahan <mahan@mahan.org> wrote:

> Okay, I wadding into the process of writing a poll-mode driver for DPDK. 
> 
> First question, is the use of the UIO device a requirement (outside of the need for interrupt support) since it is possible to map the PCI bars via /dev/mem?

Not really, the 6wind virtio driver doesn't bother (because it uses I/O ports).
But if you want link state interrupt then you need UIO support.
Plus if you use UIO, then there is protection against overlapping usage between
user mode and kernel drivers which matters especially if doing blacklisting.

The whole memory mapping approach in DPDK needs to be hardened with something
stronger like using the IOMMU. Recent kernels support something called VFIO
which could be used. This is a base PCI level change, not a something each driver
should have to worry about.

  http://lwn.net/Articles/474088/


> 
> Second question, is it expected that the NIC hardware would already have been initialized by the kernel driver for that device? Say to load microcode on an intelligent NIC?

If you need firmware then yes, the linux firmware loader is a lot easier
than doing it yourself. I wouldn't assume more than that.

      reply	other threads:[~2013-07-31 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 21:23 Patrick Mahan
2013-07-31 21:35 ` Stephen Hemminger [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=20130731143518.7eee47cf@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=mahan@mahan.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).