DPDK patches and discussions
 help / color / mirror / Atom feed
From: Fan Zhang <roy.fan.zhang@intel.com>
To: dev@dpdk.org
Cc: pablo.de.lara.guarch@intel.com
Subject: [dpdk-dev] [PATCH v2 0/2] crypto/scheduler: add mode specific parameter support
Date: Mon, 23 Jul 2018 14:17:13 +0100	[thread overview]
Message-ID: <20180723131715.62875-1-roy.fan.zhang@intel.com> (raw)
In-Reply-To: <20180622120847.72376-1-roy.fan.zhang@intel.com>

This patch adds scheduler PMD mode specific parameter support. The              
packet-size-distr mode now support custom threshold during initialization.

v2:
- Rebased to master (thanks to Pablo)
- Fixed documentation

Fan Zhang (2):
  crypto/scheduler: add mode param parsing
  crypto/scheduler: add packet-size-distr mode param parse

 doc/guides/cryptodevs/scheduler.rst                | 12 +++-
 drivers/crypto/scheduler/rte_cryptodev_scheduler.h |  1 +
 drivers/crypto/scheduler/scheduler_pmd.c           | 75 ++++++++++++++++++++++
 3 files changed, 87 insertions(+), 1 deletion(-)

-- 
2.13.6

  parent reply	other threads:[~2018-07-23 13:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 12:08 [dpdk-dev] [PATCH " Fan Zhang
2018-06-22 12:08 ` [dpdk-dev] [PATCH 1/2] crypto/scheduler: add mode param parsing Fan Zhang
2018-06-22 12:08 ` [dpdk-dev] [PATCH 2/2] crypto/scheduler: add packet-size-distr mode param parse Fan Zhang
2018-07-23 13:17 ` Fan Zhang [this message]
2018-07-23 13:17   ` [dpdk-dev] [PATCH v2 1/2] crypto/scheduler: add mode param parsing Fan Zhang
2018-07-23 13:17   ` [dpdk-dev] [PATCH v2 2/2] crypto/scheduler: add packet-size-distr mode param parse Fan Zhang
2018-07-24  8:17   ` [dpdk-dev] [PATCH v2 0/2] crypto/scheduler: add mode specific parameter support De Lara Guarch, Pablo

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=20180723131715.62875-1-roy.fan.zhang@intel.com \
    --to=roy.fan.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.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).