From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) by dpdk.org (Postfix) with ESMTP id F01339DE for ; Wed, 4 Dec 2013 12:45:33 +0100 (CET) Received: by mail-vc0-f170.google.com with SMTP id ht10so11328683vcb.15 for ; Wed, 04 Dec 2013 03:46:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=o87nrDb2/QHXzblhMbHaL10d6YhbUAZqaFceeozFZdk=; b=Ei+O8CIVzp3PoAqVSQl/Q1ua+B5GqKAHuMmv3wdNnHfnwX1MHBywCKyB4VatJnv2Db nlo9kjfgUOdtrfe7IYJ8FTPd+pBmO6+Dk8mSyjq9Ap2jwKk7kiD4ofYFojTbhrA/mozz lOm4qrDaXgdze/RSLiXlumBcQ7fWSRl5as/GjLldl7/JyGBVXfHnjkty3UFLGMQf1Qxc D+7M21JvG70qfJ9jyaBCx+lCKg+4q7pR9Rk8iP0NzrYjaYohCyfi5bCZffa0ef0j835y W09bFy9vCSeJez89OJR4rJrZT3jOTIQx7K9k6x2rHvIm9YvfWBvtK2Xo6k8EdbciJ0RN KCdQ== MIME-Version: 1.0 X-Received: by 10.52.171.198 with SMTP id aw6mr408638vdc.51.1386157596085; Wed, 04 Dec 2013 03:46:36 -0800 (PST) Received: by 10.52.177.70 with HTTP; Wed, 4 Dec 2013 03:46:36 -0800 (PST) Date: Wed, 4 Dec 2013 03:46:36 -0800 Message-ID: From: Sambath Kumar Balasubramanian To: "dev@dpdk.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Question on the Ring Library X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 11:45:34 -0000 Hi, The ring library seems to be an excellent IPC. But looking at one use case where the fast path code posts events to event thread for example, the event thread will spend some cycles polling the ring rather than waiting for the event. One approach could be a fast path code basically posts the event in the ring as is today and there is a background thread that polls the queues and wakes up the event threads. This is similar to Linux SOFTIRQs.The event threads are asynchronous. Is this a fair model to avoid extra polling CPU cycles by the event threads? Is there any other alternatives in dpdk? Regards, Sambath