From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759436AbaD3Qfu (ORCPT ); Wed, 30 Apr 2014 12:35:50 -0400 Received: from ns.mm-sol.com ([37.157.136.199]:38906 "EHLO extserv.mm-sol.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759365AbaD3Qfq (ORCPT ); Wed, 30 Apr 2014 12:35:46 -0400 Message-ID: <5361265D.2000706@mm-sol.com> Date: Wed, 30 Apr 2014 19:35:41 +0300 From: Stanimir Varbanov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 MIME-Version: 1.0 To: Herbert Xu CC: "David S. Miller" , Grant Likely , Rob Herring , linux-arm-msm@vger.kernel.org, Mona Hossain , Hariprasad Dhalinarasimha , Zhen Kong , Niranjana Vishwanathapura , Rohit Vaswani , linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [RFC PATCH v2 1/9] crypto: qce: Add core driver implementation References: <1397479725-20954-1-git-send-email-svarbanov@mm-sol.com> <1397479725-20954-2-git-send-email-svarbanov@mm-sol.com> <20140428085928.GA16310@gondor.apana.org.au> In-Reply-To: <20140428085928.GA16310@gondor.apana.org.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Herbert, On 04/28/2014 11:59 AM, Herbert Xu wrote: > On Mon, Apr 14, 2014 at 03:48:37PM +0300, Stanimir Varbanov wrote: >> >> +#define QCE_MAJOR_VERSION5 0x05 >> +#define QCE_QUEUE_LENGTH 50 > > What is the purpose of this software queue? Why can't you directly > feed the requests to the hardware? Good question. This is a leftover from original driver. The hardware can handle one request at a time. After you raise the question I think the queue length should be 1 or remove it completely. I don't know why the original codeaurora's driver use 50. > > If the hardware can't handle more than 50 requests in-flight, > then your software queue has failed to handle this since you're > taking requests off the queue before you touch the hardware so > you're not really limiting it to 50. That is, for users that > can wait you're potentially dropping their requests instead > of letting them wait through the backlog mechanism. -- regards, Stan