DPDK usage discussions
 help / color / mirror / Atom feed
From: Scott Daniels <daniels@research.att.com>
To: users@dpdk.org
Subject: [dpdk-users] Proposal -- Add APIs allowing for VF management
Date: Fri, 15 Jul 2016 14:06:35 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LSU.2.20.12.1607151400020.12469@localhost> (raw)



The need to configure and manage virtual functions (VFs) on a NIC in order 
to apply policy has grown to the point that we have implemented a small, 
DPDK based, tool to do so.  Our tool, VFd (Virtual Function daemon), 
allows us to configure VFs using a per VF description provided by an 
external source (e.g. a virtualisation manager such as Openstack).


In order to implement VFd, initially supporting just the Intel 82599, we 
found that not all of the NIC management could be accomplished through the
existing DPDK libraries, and would like to propose the following API 
extensions to DPDK:

    - mailbox communication callback support
    - TC configuration
    - DCB configuration
    - Queue configuration
    - PF/VF statistics

These API extensions would allow software such as VFd to manage any 
supported NIC without the need for customised code in the application.

Is this something that the community would be open to?


We also believe that once the APIs are added a more generic management 
tool, similar to VFd, could be added to allow for VF management via 
traditional command line tools (ifconfig, ip, ethtool). This could be 
maintained either as one of the DPDK examples, or as a separate community 
supported software application.

Again, we're wondering what the community thinks about such a tool.


Scott

VFd is open source and is hosted on github:
https://github.com/att/vfd


------------------------------------------------------------------------
E. Scott Daniels
PMTS - Cloud Software Research
AT&T Labs - Research

             reply	other threads:[~2016-07-15 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 18:06 Scott Daniels [this message]
2016-07-18  8:46 ` 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=alpine.LSU.2.20.12.1607151400020.12469@localhost \
    --to=daniels@research.att.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).