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 C2316A034C; Wed, 21 Dec 2022 10:19:41 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id ACC0040A7A; Wed, 21 Dec 2022 10:19:41 +0100 (CET) Received: from mail-qv1-f47.google.com (mail-qv1-f47.google.com [209.85.219.47]) by mails.dpdk.org (Postfix) with ESMTP id 8905C40698 for ; Wed, 21 Dec 2022 10:19:40 +0100 (CET) Received: by mail-qv1-f47.google.com with SMTP id o12so9963909qvn.3 for ; Wed, 21 Dec 2022 01:19:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:content-language:references :to:subject:from:user-agent:mime-version:date:message-id:from:to:cc :subject:date:message-id:reply-to; bh=7KZvNSSDUX+CUwBsHkvs9cgZjc33aWykicp6+sTP+qY=; b=dRD8+4wS+pBmZfPsEPWhXGNmOqDwrRCmahfJXKxolLqnAZXcittacdNFwgVSurxcnz ncr1h/UjAjauYA90J3Jo3OwWi+gEpPJPcE0xWQEV5mcm8Kh9Y9d3tZroVWuqFWpLz+4f 2KJ7BxNOJCSHF4j9xiX+MI2c7UGGKQNdQleL/hXuYJ8200NbYoZDFvr8mfW1cbArMhV6 ivH+ZZXYeni2heoku1gDhtmbz3ES5itq68CyxcCuAvJ6UUvoLMCUjKg+Co142zTepuDs 7XoFCus7ADKWnrQDbwulB3aq9fvxUsO71vYing3X66R4ubYt45FLsTcrYzx3QXIWNkzZ 0C4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:content-language:references :to:subject:from:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=7KZvNSSDUX+CUwBsHkvs9cgZjc33aWykicp6+sTP+qY=; b=W05SnprGC7KB674+/Z6Pve3j+PmA6rCxJ5LPo7dBle9HVWbUgVTPTJdCvF6omZ5eWn SO70aEK3e+KyA84Co6u+U1P1JdUi5AssW4J88vo5yGfr/tTVq0IhSHhWlEaaxbBs29qd 6nIFL09QYap1EXHz8nW+o7RsUxBHpbgtOQFdgup7Dku6guMQXJRl1e2+wlMVB/LOHu4F Fazc6q/oOTVMNTizwSf6yrdBxDmgTbMm+aQuEwunmm1uh6lH5aIsJl0WhiPeLbmVd8vL iydvS5IvRT2Fp5O0deEW8DzmS5ZPVzIBIsb5p4PInSXlmfuB5SAvUNa5mpD7BdFHDRnV YKpw== X-Gm-Message-State: AFqh2kp8tyOQqZc5QpiS9/4hizTovMpeAepq4oxLaDN4QvS3wbjFg4c4 MNQ3wIWjX3xE1NR4NFE5/jRFWIq1yRcMFz/D X-Google-Smtp-Source: AMrXdXt9LOiFhmCFazsPkUpIQUUTGjCpVC8sqOAdf+u7o8n4u2sj3jNCJMiPzJ4Tmu8GQjWT0NDFQg== X-Received: by 2002:a05:6214:5709:b0:4c6:e1ba:b1a with SMTP id lt9-20020a056214570900b004c6e1ba0b1amr1694708qvb.10.1671614379674; Wed, 21 Dec 2022 01:19:39 -0800 (PST) Received: from [10.249.156.64] (nat-216-240-30-25.netapp.com. [216.240.30.25]) by smtp.gmail.com with ESMTPSA id g4-20020a05620a218400b006b95b0a714esm10271989qka.17.2022.12.21.01.19.38 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 21 Dec 2022 01:19:39 -0800 (PST) Message-ID: <25f07e33-1122-5fb2-9384-9bdee0a892fa@gmail.com> Date: Wed, 21 Dec 2022 09:19:35 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 From: "Zhang, Fan" Subject: Re: questions about crypto_scheduler To: dev@dpdk.org References: <3637a6bf-beee-0994-203c-69c9a77a3042@linaro.org> Content-Language: en-US In-Reply-To: <3637a6bf-beee-0994-203c-69c9a77a3042@linaro.org> 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 Hi Zhangfei, The crypto scheduler PMD's session contains "sub-sessions" for all works, 1 sub-session per driver ID, to minimize the memory footprint. When configuring session, it configures the sub-sessions one by one. Since your UADK devices sharing the same driver ID, the crypto scheduler will only create one session for them to share. Hope this answers your question. Regards, Fan On 12/16/2022 6:54 AM, Zhangfei Gao wrote: > Hi, Akhil > > Excuse me for the question. > > I am testing UADK crypto performance with dpdk-test-crypto-perf, and > want to use multi-thread or multi-session for better performance, so > trying to use crypto_scheduler. > > CMD like > sudo dpdk-test-crypto-perf -l 1,2 --vdev "crypto_uadk0" --vdev > "crypto_uadk1" --vdev > "crypto_scheduler,worker=crypto_uadk0,worker=crypto_uadk1,mode=round-robin" > -- --devtype crypto_scheduler --optype cipher-only --buffer-sz 8192 > > Though multi-worker is set but found it is just using one worker. > Since uadk_cryptodev_probe gets the same dev->driver_id = > uadk_cryptodev_driver_id in multi-probe. > > Then scheduler_pmd_sym_session_configure will treat only one worker, > and call rte_cryptodev_sym_session_create only once. > if (configured_sess[j].driver_id == worker->driver_id) >         break > > Do I misuse the crypto_scheduler for the multi-thread or multi-session. > > Thanks in advance. >