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 C1F2EA0542; Fri, 16 Dec 2022 10:27:21 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6B8BA42C4D; Fri, 16 Dec 2022 10:27:21 +0100 (CET) Received: from mail-wm1-f41.google.com (mail-wm1-f41.google.com [209.85.128.41]) by mails.dpdk.org (Postfix) with ESMTP id 019DC40685 for ; Fri, 16 Dec 2022 10:27:20 +0100 (CET) Received: by mail-wm1-f41.google.com with SMTP id f13-20020a1cc90d000000b003d08c4cf679so1266993wmb.5 for ; Fri, 16 Dec 2022 01:27:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=7KZvNSSDUX+CUwBsHkvs9cgZjc33aWykicp6+sTP+qY=; b=Mwcu7qSDoqAmBY2HCLeHEyivAatXYp1vep52BgxDNdGYKIC859K2UEtzImgfCka7wx +e9Nbp55DzkpUR7O/JNOIEKT276uB/jHZXJYG126zxskzXw73uIUCk8uifUyW4II4ztw dp5as+Om9Arm6vBAcmDuRJrT5uVx72nijxtMhC5xlT0rOL3NGvGC6R2s3aopVatYK9mg jBHy6I+08EXj3hjses1OQg7IduWh9YvXOAsXgBVOhjaW3C9nRD84cq83ECTAsIjyoszD /J80MZEkdoF387ekAidnWKkWn1KLNX3f8QoBZmm+VCmTr/b492kQcKNynQUnPvkReKVz +IYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject: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=tht1YMnxtxAUxfiRw5C/cguJPKFtvE+lUOG5FNjJdtc10zmYs/kRjLAlmJP99kNMth nNTx9h2F1Nk8ETdgVLOQF3SXT5L/Y9BouJ+jzS6ryxudrnWmk6CYc5E0GPUyQ9XrJ7b0 3+chFl6zgAWUmfkM9TL9ZwVo4tBCkSKVoirz2KcoD/90A0Uzi4yiS7aALwo5w2Kbjjtc xs3cxqkT5lDgZ20l1B8xiFCfSmvujBp72qtw8/pxt5DiOS4Le0SD+SGL1GU83B497p+v 0PhMHYEkCgGdVyS8YVSs+ezUpRYcrSxnKkB9wXyHjkEseOqUo/Y6yTvDpWutdPrn5ZSH ICng== X-Gm-Message-State: ANoB5pmPGsvbkw1/+5ATCWSjApbKfvTcQE2wNNCzugmGTi2LoL81J1Bd 74lEz1hwgXvuDSw55tgQMwLQbU5oqkQMIw== X-Google-Smtp-Source: AA0mqf4l2Ou8h/EptWVLUP7Z6kz3OLKPf/XhHufnyDblVA8dImyeffhPAO4AyN21xU4TMlZTT7Q/+w== X-Received: by 2002:a05:600c:4f14:b0:3cf:e91d:f263 with SMTP id l20-20020a05600c4f1400b003cfe91df263mr24345782wmq.4.1671182840453; Fri, 16 Dec 2022 01:27:20 -0800 (PST) Received: from [192.168.195.161] ([80.233.47.243]) by smtp.gmail.com with ESMTPSA id j42-20020a05600c48aa00b003d1f3e9df3csm8267703wmp.7.2022.12.16.01.27.18 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 16 Dec 2022 01:27:19 -0800 (PST) Message-ID: Date: Fri, 16 Dec 2022 09:27:17 +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 Subject: Re: questions about crypto_scheduler Content-Language: en-US To: dev@dpdk.org References: <3637a6bf-beee-0994-203c-69c9a77a3042@linaro.org> From: "Zhang, Fan" 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. >