From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0FA3BA0350 for ; Wed, 1 Jul 2020 11:49:06 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6860F1D146; Wed, 1 Jul 2020 11:49:05 +0200 (CEST) Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) by dpdk.org (Postfix) with ESMTP id 8A2331C434 for ; Wed, 1 Jul 2020 11:49:04 +0200 (CEST) Received: by mail-wr1-f41.google.com with SMTP id a6so23124358wrm.4 for ; Wed, 01 Jul 2020 02:49:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=K5X+PZu6W+LYBTEa8TTniYvJn9T8N+qOixrWC6LKlpY=; b=dXlpiXkdLctcftNPTxRSCOfiXoAv2nsOy7xK+LWxCTdmSNZ9BhHdtxWhg2ycCGEYgY 90FLIIgYaSG3L7Raxn1SItB+SLlEecIjmfkWsa9x/jPzBHm3+BS3kJIUFQz/xr5zkEcG U0i+jWT0SGUB7KPQbpioY0j/8H2hK68m/+AKtla4aY2YKlpULUp1PizHWrrVOrFoFCdU d1ZKn2FNnT4AsWgiVcD/ib8tSHHNn6F5kbrMkge1Hhb2sHFOrru2V9nzG1MdRvPLgp4w o2WRinBcqgf+Px+PUjBQlustsQ+5wOwpJhYwUg0gCYYXXaeM1e431bfNZSMjL08toA4H y6ug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=K5X+PZu6W+LYBTEa8TTniYvJn9T8N+qOixrWC6LKlpY=; b=ISSpP+xehE5Qd/98GBtisRKC4cPDSz/u5/I+CgMFhBauVIPX24Lt4nRoCEUjsSKkqn ab6GcDOaOB245P8aKS7oI2kr/bhiiBAB+dUpSXMFCpnc4To/7Q1LtivwSA/lAuLF+C4T 36lMKJkaTi6W/u+gcmfSsQqGSEO8txLmLh1/X1kcwt44pkJ8JTkZywXNEmFleRtM2Qx4 47twB02zxIYiTeuTTCWtKM6ksjSx061gqJkmkT2BEneMm6MptCrxGLZYndZP2Fps+dMz JOkgPNladr556wkQVbn4FIj3/+MWshCfw0upJm+Nu2DIl/omNIzBLzSb+wmyIuN5SmDn u0pg== X-Gm-Message-State: AOAM530y0GnIJXCcm09o7FivWio6mJmeP0eQn/Tgymp9MbZYYh6/touM 7D1Td8mE9yMcU6umBc4Cuk2miZdn9xbLWFW0/xVZ2/tARc0= X-Google-Smtp-Source: ABdhPJzQbVpFK7BerGnwUh7lg7wPj1jwAbwJyNdHqMfxxs5cJbiB/qzviTP+9KJvb8rg+X5kR/3GoGidtPWjKYdsmt8= X-Received: by 2002:adf:e3c9:: with SMTP id k9mr24928784wrm.379.1593596943649; Wed, 01 Jul 2020 02:49:03 -0700 (PDT) MIME-Version: 1.0 From: Pavel Vajarov Date: Wed, 1 Jul 2020 12:48:52 +0300 Message-ID: To: users Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Handling KNI in a secondary process X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi there, Basically my question is whether it's possible to handle KNI packets (rte_kni_tx_burst, rte_kni_handle_request, rte_kni_rx_burst) in a secondary process? My idea to do this is to avoid slowing down the primary process with KNI handling. I'm thinking of using a shared memory ring buffer to send the needed packets to the secondary process (just like in the mulitprocess/client_server_mp example) and then the secondary process will do the KNI processing. Is this setup possible? I'm asking this because I read that the rte_kni_init function that "This function is to be executed on the MASTER lcore only" and I was wondering will I be able to use the kni related functions from a secondary process? Or maybe I need to initialize the KNI in the master process and then use rte_kni_get before start using the KNI? Thanks, Pavel.