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 5E586A0032; Wed, 11 May 2022 15:13:35 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EF20D40DDD; Wed, 11 May 2022 15:13:34 +0200 (CEST) Received: from mail-il1-f173.google.com (mail-il1-f173.google.com [209.85.166.173]) by mails.dpdk.org (Postfix) with ESMTP id 7B4E0406B4 for ; Wed, 11 May 2022 15:13:33 +0200 (CEST) Received: by mail-il1-f173.google.com with SMTP id 3so1402043ily.2 for ; Wed, 11 May 2022 06:13:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=XvnXpmQOr8scaeuQsEbU8AUKdNncm9l9H6aTTi5XOg8=; b=pdtLg6rDWJFR8L1vXHkaXZjJ29p48Kh9TfBEXkPKIj8mDzn/jWtrye9DoDCDfeLRr9 K7FDvXOLV2wZnbmbUUqN8u2ZNRBSn2nTHCgyozbnHHppSad9wPd95wgnjH/kkRwzmVXo vLd0RueemxXHXl/foCCqtGZ47owt/WpnZEs0QRo8qFb+C8FMkKDgJoVPxKuxyvaRPvuR a1IUSobaFqt/Tgf3X5GuanEYUJuj1xKqQnkzWS8oFjXPuyiM293L3EKPugVeJrrU3c78 hW6mSw3t4xlGRKQFxrPUPIxvAwkqEZplWy5uN0TJ+h71YU1X0No2LJpdlzgjM9e4Vr6u GJKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=XvnXpmQOr8scaeuQsEbU8AUKdNncm9l9H6aTTi5XOg8=; b=ZVsxIkfSYHRJHYfxarplL8+Bgx9SAEYHjZOG6Hv9H2XiWdnu9VS3Q7+JvOShJ9OTpr 3a/bQ4DZ+Ks/pUyvskAOvBCj8OgZIAUn6lxjjasq3camVHdET2jrXHcWvCtUevMjDoBh 2hzAbBdqliA8y9t2MJqUTgKJI7IwffQZ7fcu/SL8QtokWquLL0uQVpS77ls2Qv/dfEKq gI7WYeTNUGLclJ+Kdj9Xasjh83cP9PltFPwBdoXDviWtZohvtbYIYBPUYfQlDNPyGwje QFcL1UyOV5r0Ut6zEYx9l9QBxGDmV+OzevWrl9jFnVMdIpQVeWtEWx/PjSwzHGjuEUJ+ JuAg== X-Gm-Message-State: AOAM532XFhaJDgwZoOoEVq/tUmi04EL46ictk5AmCsIgs8EPROoz12YF 7eL+i4PeD96+uXgcByiqg9qNDRHYeS/o7KSHtkJ1LPB8sYs= X-Google-Smtp-Source: ABdhPJxUOPFy/hYk/Btm8aFRwxDix/5DLK4Yg7IhvjYVb9RLPMWy8v/9v+io+ziSeTiMd2HfmeEd4TwRsJ66+zFlZx0= X-Received: by 2002:a92:d1d1:0:b0:2cd:73a5:f0 with SMTP id u17-20020a92d1d1000000b002cd73a500f0mr11222211ilg.161.1652274812521; Wed, 11 May 2022 06:13:32 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Maxime Ramiara Date: Wed, 11 May 2022 15:13:23 +0200 Message-ID: Subject: Re: Softnic test failed + questions To: dev@dpdk.org Content-Type: multipart/alternative; boundary="00000000000045941705debc3581" 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 --00000000000045941705debc3581 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable EDIT : The tutorial that I followed to test SoftNIC ( https://doc.dpdk.org/guides-19.02/nics/softnic.html) is appropriate for DPDK 19.02 but not for the newer versions like 19.11.12, the one I use. We found out something : " sudo ./dpdk-testpmd --vdev 'net_softnic0,firmware=3D./firmware.cli,cpu_id=3D0,conn_port=3D8086,sc=3D0'= -- -i --portmask=3D0x2". We didn't really understand the impact of "sc=3D0" by t= he way. First line of firmware.cli file : "link LINK0 dev net_softnic0" instead of "link LINK0 dev 0000:19:00.0". Then, we switched the forwarding mode to Input/Output with the CLI. With all of that, it looked like it worked. We didn't have any error messages like before. If someone is comfortable with test pmd / softnic versions, help should be quite welcome. Then, can anyone help us on the pipeline we wanna design (first e-mail) ? Regards, Max. Le mar. 3 mai 2022 =C3=A0 11:33, Maxime Ramiara a = =C3=A9crit : > Hi all, > > I'm a beginner with dpdk. With my team, we developed a dpdk app with the > following pipeline: > > NIC RX -> RX Thread -> Worker Thread -> TX Thread -> NIC TX. > > Within the RX Thread, we parse some headers. Within the worker thread, > we're using the hierarchical scheduler. To sum up, we want to replace the > HS with the traffic manager. > However, it seems the TM can only be set up on a NIC. This is not what we > want because we're doing some packet processing stuff within the TX Threa= d. > > > Thus, we thought about the SoftNIC as a solution for our problem. Would i= t > be possible to develop a pipeline like this ? > > NIC RX -> RX Thread -> SoftNIC with TM -> Worker Thread -> TX Thread -> > NIC TX. > > It looks like the "firmware.cli" script and the packet framework offer us > some freedom to make our pipeline. > First and foremost, I tried to test the SoftNIC with the following comman= d > in the doc : > > ./testpmd -c 0x3 --vdev 'net_softnic0,firmware=3D