From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] Scheduler: add driver for scheduler crypto pmd Date: Fri, 02 Dec 2016 15:31:24 +0100 Message-ID: <8047937.9v81RFizFU@xps13> References: <1480688123-39494-1-git-send-email-roy.fan.zhang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, declan.doherty@intel.com To: Fan Zhang Return-path: Received: from mail-wj0-f175.google.com (mail-wj0-f175.google.com [209.85.210.175]) by dpdk.org (Postfix) with ESMTP id 06ADDFA57 for ; Fri, 2 Dec 2016 15:31:25 +0100 (CET) Received: by mail-wj0-f175.google.com with SMTP id v7so233344084wjy.2 for ; Fri, 02 Dec 2016 06:31:25 -0800 (PST) In-Reply-To: <1480688123-39494-1-git-send-email-roy.fan.zhang@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-12-02 14:15, Fan Zhang: > This patch provides the initial implementation of the scheduler poll mode > driver using DPDK cryptodev framework. > > Scheduler PMD is used to schedule and enqueue the crypto ops to the > hardware and/or software crypto devices attached to it (slaves). The > dequeue operation from the slave(s), and the possible dequeued crypto op > reordering, are then carried out by the scheduler. > > The scheduler PMD can be used to fill the throughput gap between the > physical core and the existing cryptodevs to increase the overall > performance. For example, if a physical core has higher crypto op > processing rate than a cryptodev, the scheduler PMD can be introduced to > attach more than one cryptodevs. > > This initial implementation is limited to supporting the following > scheduling modes: > > - CRYPTO_SCHED_SW_ROUND_ROBIN_MODE (round robin amongst attached software > slave cryptodevs, to set this mode, the scheduler should have been > attached 1 or more software cryptodevs. > > - CRYPTO_SCHED_HW_ROUND_ROBIN_MODE (round robin amongst attached hardware > slave cryptodevs (QAT), to set this mode, the scheduler should have > been attached 1 or more QATs. Could it be implemented on top of the eventdev API?