DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	gprathyusha@caviumnetworks.com
Cc: dev@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/7] dpdk-devbind.py refactor
Date: Tue, 25 Apr 2017 11:30:32 +0200	[thread overview]
Message-ID: <1610572.RF2RvmXMRj@xps> (raw)
In-Reply-To: <1490191892-10396-1-git-send-email-jerin.jacob@caviumnetworks.com>

22/03/2017 15:11, Jerin Jacob:
> This patchset refactor the dpdk-devbind.py script to
> 
> 1) Optimize the bind and status operation delay(It is noticeable
> when the system has fairly large number of PCIe device. For instance,
> OCTEONTX system has around 170 PCIe devices and it takes around
> 19 seconds to bind devices. With this patch it is reduced to less
> than one seconds)
> 
> Patch 3 and 4 address this optimization
> 
> 2) There is a lot of common code in NIC and crypto device
> to get the device info, display status.
> 
> Patch 1 and 2 create a common code to add new devices
> without duplicating the code
> 
> 3) This patch creates the framework to define the DPDK PCI functional
> device by specifying the pci attributes like Vendor ID, Device ID,
> Sub Vendor ID, Sub Device ID and Class.This enables a flexible way to
> add DPDK function devices based on PCI attributes.
> 
> Crypto devices can belong to Encryption class(0x10) or Processor
> class(0x0b) based on the vendor preference.
> 
> Using this framework, The above disparity can be encoded in the following
> format
> 
> encryption_class = [{'Class': '10', 'Vendor': None,
>                      'Device': None, 'SVendor': None, 'SDevice': None}]
> 
> intel_processor_class = [{'Class': '0b', 'Vendor': '8086', 'Device': None,
>                         'SVendor': None, 'SDevice': None}]
> 
> crypto_devices = [encryption_class, intel_processor_class]
> 
> 4) Add eventdev, mempool PCI devices support
> 
> Guduri Prathyusha (7):
>   usertools: refactor the get NIC and crypto details
>   usertools: refactor the show status function
>   usertools: optimize lspci invocation
>   usertools: use optimized driver override scheme to bind
>   usertools: define DPDK PCI functional device
>   usertools: add eventdev PCI functional device
>   usertools: add mempool PCI functional device

Applied, thanks

      parent reply	other threads:[~2017-04-25  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 14:11 Jerin Jacob
2017-03-22 14:11 ` [dpdk-dev] [PATCH 1/7] usertools: refactor the get NIC and crypto details Jerin Jacob
2017-03-22 14:11 ` [dpdk-dev] [PATCH 2/7] usertools: refactor the show status function Jerin Jacob
2017-03-22 14:11 ` [dpdk-dev] [PATCH 3/7] usertools: optimize lspci invocation Jerin Jacob
2017-03-22 14:11 ` [dpdk-dev] [PATCH 4/7] usertools: use optimized driver override scheme to bind Jerin Jacob
2017-03-22 14:11 ` [dpdk-dev] [PATCH 5/7] usertools: define DPDK PCI functional device Jerin Jacob
2017-03-22 14:11 ` [dpdk-dev] [PATCH 6/7] usertools: add eventdev " Jerin Jacob
2017-03-22 14:11 ` [dpdk-dev] [PATCH 7/7] usertools: add mempool " Jerin Jacob
2017-04-25  9:30 ` Thomas Monjalon [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=1610572.RF2RvmXMRj@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gprathyusha@caviumnetworks.com \
    --cc=jerin.jacob@caviumnetworks.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).