From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f179.google.com (mail-qk0-f179.google.com [209.85.220.179]) by dpdk.org (Postfix) with ESMTP id A6EF72BAA; Wed, 10 May 2017 18:14:00 +0200 (CEST) Received: by mail-qk0-f179.google.com with SMTP id k74so334713qke.1; Wed, 10 May 2017 09:14:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8excBLLq4CdTfGx7WvG46Yl+7zA3XO4r9vSvY7lwwPU=; b=mLXO8I9gxqEF0P+d/xls2pPNhGUGW7DTXodjnhUSIm9B3PdqLJoNaobZjB6ZyrtBlE 3r7QWFuUOQ+BPHssswBSHM3Y7WwUutSnm4XrV/26DMYfU3ftETggttl1nekdfwoHEGCv d0RY8bK8TniLZw2A6vv8V3wZmlCpVC4e8x5WSFe/PlK/QjXi0vnk9P98rBFBhyPciERk pg8elB+CLNkzvT3Jl69qfZnnykgQASc+Vqmz9PnhtTjy0WNbaxR323UCkCyt9+keQNAA /7fqhBf9y6O2nwnaewnfwGoioFIqqBWKuKCQTFU4AA+i4yFmh9Pn4YzzfdVheyQHTuaL MqRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8excBLLq4CdTfGx7WvG46Yl+7zA3XO4r9vSvY7lwwPU=; b=dMN4Evnow3CL726a2rbgf9dKDtEvOXs+ICjZbP4Nv+cNAdP/HU/KkcSd+yybNi5PbV SxAyZtVfiBFxCN1pWfsbrYPhKlj0um8JNwVBxtiZym6Mk5Pw6l3kSKXcyiyxK0OGBr+6 elxMT3NpMbRTmQF4JoWdbZGAUCdj4AOIg0cqZ+ZLWXYKUhD6wgF8ZVA8e37R8r7ATECK RiQ8gqr8kuMt9wW6nH9qdsmNjpKAwB/BHe2jxDJb3zubb7taIhIpsyUw+p0cHHfhrdCs JH5wTV5W65KrdW1Cj+8A1xCRm42hLXy9l0ruWtTmcVuB5mM5CvRFFaXcbrUSp7ziqt85 Atog== X-Gm-Message-State: AODbwcBbkQPqwlXn3B4iodvYl4xFIm2J24MXbTr4nWu8vVJH8w8UacqJ Yjaocu3Pg5+ncN2DiuJ+D5e+UkWOPg== X-Received: by 10.55.136.3 with SMTP id k3mr5973883qkd.283.1494432840113; Wed, 10 May 2017 09:14:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.172.76 with HTTP; Wed, 10 May 2017 09:13:59 -0700 (PDT) In-Reply-To: References: <54CBAA185211B4429112C315DA58FF6D31B5F93E@IRSMSX103.ger.corp.intel.com> <3EB4FA525960D640B5BDFFD6A3D8912652798F27@IRSMSX108.ger.corp.intel.com> From: Shyam Shrivastav Date: Wed, 10 May 2017 21:43:59 +0530 Message-ID: To: Nidhia Varghese Cc: "Dumitrescu, Cristian" , "Singh, Jasvinder" , "dev@dpdk.org" , "users@dpdk.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] [dpdk-dev] Fwd: Sharing tables among pipelines 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: Wed, 10 May 2017 16:14:00 -0000 Something I have gathered reading through code if it helps, ip_pipeline is designed such that user side cli (_fe) runs in master pipeline and sends conf requests to various other packet processing pipelines (_be) which handle such requests at intervals. These can run on same or different threads(cores) as per conf, no locking requirement as table-updation & table-reading (packet processing) always happens in same pipeline so always same thread. Master pipeline can be configured to run on a separate core & it should be the case, but table updation happens in pipeline thread only at lower priority. On Tue, May 9, 2017 at 11:29 PM, Nidhia Varghese wrote: > Hi all, > > Thanks for your reply. > > As given in the link(3rd point), what I need is single writer > thread(pipeline) performing table entry add/delete operations and another > thread(which is in turn another pipeline) that performs lookup operations > to the same table entries. > > > Thanks, > Nidhia Varghese >