From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb1-f173.google.com (mail-yb1-f173.google.com [209.85.219.173]) by dpdk.org (Postfix) with ESMTP id 6ADF34C9C for ; Mon, 5 Nov 2018 14:46:00 +0100 (CET) Received: by mail-yb1-f173.google.com with SMTP id 131-v6so3769266ybe.12 for ; Mon, 05 Nov 2018 05:46:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Gtu8ACyxkFqI9a82stjuS5EC6kxA9LI+UAd1ULmPIVo=; b=DvxyhIGIpnh2ChiHF+hUk1ZxoIAaTXcxfzAf9TsTkYjbMLbf6kbymDidrpohRwmh+u 4vFbKYWn2LD72rbjRo3LUSR3AbFV8AvX+DbIxTwt4lbdrJ1Ceeg+fo3ORQNnHx0t0dQ8 aOpWZEaBrHtWm3VDKR9hcSNBqzsrHykHvw9zD71XcvHhywOs9FDR8y6mmap4JWf5g/b/ AirSX/dRYpAL/qI3wqnGhJcg7TY+pVvn8cjvgRPmiHxu6SFAZVoNUDiHYvhMl3yQl1yO LiB8Fc5zUjbkQxvtVRIm7C/FY4FG4eIDP7moKNAsrIQ2zKdh4YRdyLlKhb13YriKofb9 1+Rw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Gtu8ACyxkFqI9a82stjuS5EC6kxA9LI+UAd1ULmPIVo=; b=m3YP+NJugiJv/ZqHUEnNQx91xlmBs8P3bxP7p21aAUt8XZzkJVJKeycmvolfXMjSwd HfYK52VsH2q1icsE5y5vDjtbMHRZMREoMEx7JBQ8pppb//dfz2I1pg3uIwVFqSSKDB/s gptbDNDMfg36LtEwUqnTlfFG0TvAts+xAHkBVSXBfGhbDve4QBD72MHGE1O3XxXCt7sG WQ96aX1O+V23nQU4etuuMJdrvwV+mZ7dsW++7/Lzkk0hpBARTYDphicAPdEOlv2hc/Rr nWRwnFGoO2DH0HQgdf4nrWso0XqxQHJlOTEB7YxSt92XuQPzKLL17bGNMeZnteO7ntNC Ruiw== X-Gm-Message-State: AGRZ1gKg8X4j3SFAu1WoqCT5V/+UcKKNjefhrpD1uf+WbN2rd0wj5MBy W0lEGQ/Z0USLrLSmY4A+S5YOOGMuk7E2gehWkFw= X-Google-Smtp-Source: AJdET5cxgAe4VmqqzirWAMdEVdAmDuF37TlYPMihbXaarO6zw90MNdzBMko1UV0OY426deO4xBrw3xqfLCyqeeAb9eM= X-Received: by 2002:a25:b284:: with SMTP id k4-v6mr22116751ybj.434.1541425559518; Mon, 05 Nov 2018 05:45:59 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Cliff Burdick Date: Mon, 5 Nov 2018 05:45:48 -0800 Message-ID: To: Kusuma DS Cc: users Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Question on Multiple process support Application 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: , X-List-Received-Date: Mon, 05 Nov 2018 13:46:00 -0000 On Mon, Nov 5, 2018, 04:56 Kusuma DS Hii, > > I have some doubts regarding multiple process example application. > > I have 2 processes running in my setup using multiprocess client and server > concept, am doing rx_burst in server process and tx_burst in client > process. But the thing is i have one isolated cpu, So both the process are > sharing the cpu. > > What i understand through the document provided by the dpdk is In the > concept of memory pool there will be per core cache lock, so if we try to > do tx and rx in different process there will be software cache problem will > occur, so there will be corrupting the memory in shared memory pool. > > How to resolve this issue??If anyone Know about this issue please let me > know. > The documentation specifies you can't lcores across processes: "All DPDK processes running as a single application and using shared memory must have distinct coremask/corelist arguments. It is not possible to have a primary and secondary instance, or two secondary instances, using any of the same logical cores. Attempting to do so can cause corruption of memory pool caches, among other issues." Have you tried two cores? > Thanks, > Kusuma >