From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D179E42C6D; Fri, 9 Jun 2023 12:20:03 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A8A3B40EDB; Fri, 9 Jun 2023 12:20:03 +0200 (CEST) Received: from mail-pf1-f177.google.com (mail-pf1-f177.google.com [209.85.210.177]) by mails.dpdk.org (Postfix) with ESMTP id 616F240A84 for ; Fri, 9 Jun 2023 12:20:02 +0200 (CEST) Received: by mail-pf1-f177.google.com with SMTP id d2e1a72fcca58-653fcd58880so1340518b3a.0 for ; Fri, 09 Jun 2023 03:20:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1686306001; x=1688898001; h=content-transfer-encoding:in-reply-to:from:references:cc:to:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=mhGg0P10P+bxXBX167nPLeDsx5pODj5ricM/m1thV8M=; b=Y95bKqBvJ3zsGcsZWLFMzVTTM5zyzRStb757L3UHk2ncmAmCU6yZdYtW/KGy/zQjmh ZF9EwkGwQxKiDmqGKSQUAKnv02gpJ1J7hepdOoPfxXcWwrIYSPNfGMRVpNFN6VvmZThS ys4TsYPHO5F7BG8IrBALSTP5bjCWRvFGQ0CtT46Idf9crJhh0sYQiBTdfGOCkhHPiCdZ L5GyIfl95T6gqkDC3VBl7PAJElZ7WMEQT1v4TIO5fCMcig5MDu3mxV3PZQNwnjnk04I0 TyZ0weRAsyu5n4Qb4wk4xAFohyl4vXlgzjiwEY5S8fY66aIVFddiLyra0f+jH5Je9zCU 4T8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686306001; x=1688898001; h=content-transfer-encoding:in-reply-to:from:references:cc:to:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=mhGg0P10P+bxXBX167nPLeDsx5pODj5ricM/m1thV8M=; b=byWVAC6rTAeV4vxg9OX97P6HrAgAVQXk0Svg1tJ7/4Orhdwcx58HOFKSCZ9XGxXcTq SAO1/D/UnGl8txSun8Sn5ctMPoAUPEIhr5FnaXBB0q/1kwJpJSoYwY0Ogl7btYZUP0dn BtqiZ2kp73X/aN6XA4AMMx9PjyUqUGFhc8AkNDH2khjE0bM4yg10xdwRVqbccIw89ouD UB0pyJLgD446tsV0/PMaT/LYOs3tHx11Q14L0JdHNuzu/HEclgcL+1SwASksV6/ZKMdU fgqTYiXFKZd2AAqy4Dma46VBOHMHyf6ZDRgPyXwRZOUgr6/byEfljZKC/XOyQiESdGwS Ic6A== X-Gm-Message-State: AC+VfDzyMskaprp5nAX6mTciLcA7ZIY1JSOkRuQL3duNKCTJFYkpmkDY 7I5881zG1Ha/1nTrA93B43CDczbH4SLSiAJBMoo= X-Google-Smtp-Source: ACHHUZ7taV3i+XaFXpztSt16D5ubSXm+0MZ7U0EGJItTpxXyvNARMHZc0apRcFKDABg59F3bCf1tvw== X-Received: by 2002:a05:6a20:8f1f:b0:10c:67c9:e5ea with SMTP id b31-20020a056a208f1f00b0010c67c9e5eamr610712pzk.31.1686306001482; Fri, 09 Jun 2023 03:20:01 -0700 (PDT) Received: from [100.64.100.6] ([199.101.192.34]) by smtp.gmail.com with ESMTPSA id 5-20020aa79145000000b0064cb6206463sm2375448pfi.85.2023.06.09.03.19.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 09 Jun 2023 03:20:00 -0700 (PDT) Message-ID: <485ae621-acf0-6dfd-6792-849cf5cc2010@linaro.org> Date: Fri, 9 Jun 2023 18:19:57 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [EXT] Re: [PATCH v2 resend] crypto/uadk: set queue pair in dev_configure To: Akhil Goyal Cc: "dev@dpdk.org" References: <20230420021313.66733-1-zhangfei.gao@linaro.org> <20230602030436.7829-1-zhangfei.gao@linaro.org> <830aa127-0794-6e7d-681a-64b14f070c38@linaro.org> From: Zhangfei Gao In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 在 2023/6/9 16:31, Akhil Goyal 写道: >> Hi, Akhil >> >> >> 在 2023/6/2 11:04, Zhangfei Gao 写道: >>> By default, uadk only alloc two queues for each algorithm, which >>> will impact performance. >>> Set queue pair number as required in dev_configure. >>> The default max queue pair number is 8, which can be modified >>> via para: max_nb_queue_pairs >>> >>> Example: >>> sudo dpdk-test-crypto-perf -l 0-10 --vdev >> crypto_uadk,max_nb_queue_pairs=10 >>> -- --devtype crypto_uadk --optype cipher-only --buffer-sz 8192 >>> >>> Signed-off-by: Zhangfei Gao >> >> Would you mind taking a look at this patch? >> > I plan to take this patch in RC2. > RC1 is mainly for large features and library changes. Thanks Akhil