From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f51.google.com (mail-wm0-f51.google.com [74.125.82.51]) by dpdk.org (Postfix) with ESMTP id 611442C01 for ; Mon, 18 Jul 2016 10:46:08 +0200 (CEST) Received: by mail-wm0-f51.google.com with SMTP id f126so93886349wma.1 for ; Mon, 18 Jul 2016 01:46:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=rGFH8VHaJ+oIxAIT85icyPt9FxrkaD1yzKE344lgXto=; b=icIz/PUuccrgRypN6vwmcGbOORrgj9SgbL2qdeGhqJZBj9nGdN2sceIVRB9kSVqSNl p1YB02C59jnNsWYExi6wgHjZdfdBdan1EHHcWyP+fSI9AixoDFkdBwyg5yEYmPcxEjoj BMA3XXBFAjlHACh4w0jq/fyvLwO0l+JOdCPNTqw4ChRODboqEZcKiheew0jF6cj3/lc5 T7vWioiZqafarEJ/1GNUQqxQxgCjRW8aScuhIaVWtiK4XEYxlEFJfwJP/9EpLTpb7XjQ 8JPPI2FYnK63i+kqd4kDqeKL24e6PWaRNteOaE1we8ZJy4wHHiN5VgeLIBjOzJF6g+2n TBAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=rGFH8VHaJ+oIxAIT85icyPt9FxrkaD1yzKE344lgXto=; b=aKpINWKbyS6nyfFZaTVlfZ4AyUW6mQo1PPEluOYmTJn4JfcUh8pp5n/eRUXsqaQEBN 3hHlihn5JZq1Oy9WJBSeBLsc8KPoC4j3UVn+RBNj2IqPhNI1Lr7b8RSrk6Wp7UgrYnev R5m9gY11/jQd3+RvUE0AHGdyHimr3DB2tvWi9lglFV6Ko5dbvOn8jIDC2GxPnjoRaQVH QFE1ACXkgnASVhtnLAk5SXMyUZ3lysKTJHgstg5wehIjBB+OmpuX8upmrJW3n3/6oujq +YgVCa8xZulGgMuRuj+m6Vs4MaL+bbussm8V6dWPyLGT/MwXYjlKNO9fi5NlO3wfUPSa rFwA== X-Gm-Message-State: ALyK8tJx4dZwUWtJb4t3P1Gft+PKlxv6Em9RHsNrqxPef+WqxJrU/4497hjo6GabCe9bxUdQ X-Received: by 10.194.16.164 with SMTP id h4mr15422wjd.158.1468831568157; Mon, 18 Jul 2016 01:46:08 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id m201sm15418135wma.11.2016.07.18.01.46.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jul 2016 01:46:07 -0700 (PDT) From: Thomas Monjalon To: Scott Daniels Cc: users@dpdk.org Date: Mon, 18 Jul 2016 10:46:06 +0200 Message-ID: <1887151.Tg81hdDixp@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-users] Proposal -- Add APIs allowing for VF management X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2016 08:46:08 -0000 Hi, 2016-07-15 14:06, Scott Daniels: > 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? It is difficult to answer to this question without understanding precisely which change you need. The VFs are managed in DPDK as any other device. The configuration is done through the ethdev library. Do you mean the ethdev API is too poor for your needs? Could you give some examples please? > 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). These tools send some ioctl to the kernel drivers. I don't know if mixing DPDK and kernel drivers would be a good idea. I think it has never been tried :) > 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 Thank you for sharing. Please use the dev@ mailing list to discuss new API.