From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 5C8001B4FC for ; Sun, 5 Aug 2018 15:40:13 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E3EFC21B2A; Sun, 5 Aug 2018 09:40:12 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 05 Aug 2018 09:40:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=4XNCmR5R/UEpeN7zNrUH6dAJBC oHFsKo1G6VvGpC4yY=; b=BGNm57QDImdFi3CRt0XnmPXuY+heCq6pdcQcGMYZyo jroV9LxommXHVA8KLQy3C3o33UZDYekTBmVlEE43IJgEaFD2WPmnKzRWuKtuCP2E t9GRXrO/DaJWeD92r2leOTXuR1nRSsER/+4+fpv743s/OIlyPems3xKAb4V1Juq4 s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=4XNCmR 5R/UEpeN7zNrUH6dAJBCoHFsKo1G6VvGpC4yY=; b=kYkKBc1nDV09MttyRtqqci 54Q6jfkiI8lCAB1XVt32r2SFf0oQd7Fd7T8NTEz0LFuhTBxN+gkm2/3b1D91fMS9 l4ddv+s37biKpYoPKQR+WHNtcW+tjF6dw/NGRMhmJRmJFumbZNs3zs7cOX3qQS3L 0snCCzFuvlRh4uEQ4JBxmd6jrnizSTyVKQylpo71Fy+mGN6O19ItpYr7nCcDH7PF CqvJQCRbmiXhzVPcpX0f37SKygY2iAUF/UFR96X4uROsLQ5lupp6dtW90Icr+Pfx 7nLrD+/tv8qPugN53Ps2XWqM7w0ZmV0W7B+Q6c43ovMAzoNliFBvHiOOULFkUBIA == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (221.87.136.77.rev.sfr.net [77.136.87.221]) by mail.messagingengine.com (Postfix) with ESMTPA id E19DCE4040; Sun, 5 Aug 2018 09:40:09 -0400 (EDT) From: Thomas Monjalon To: Honnappa Nagarahalli Cc: dev@dpdk.org, Olivier Matz , anatoly.burakov@intel.com, nd@arm.com Date: Sun, 05 Aug 2018 15:40:06 +0200 Message-ID: <90205331.zdikCl6GkY@xps> In-Reply-To: <20180803150926.dxuheyyi75xd67y4@platinum> References: <1531803164-46516-1-git-send-email-honnappa.nagarahalli@arm.com> <20180803150926.dxuheyyi75xd67y4@platinum> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4] rte_ring: clarify preemptible nature of ring algorithm X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Aug 2018 13:40:13 -0000 03/08/2018 17:09, Olivier Matz: > On Mon, Jul 16, 2018 at 11:52:44PM -0500, Honnappa Nagarahalli wrote: > > rte_ring implementation is not preemptible only under certain > > circumstances. This clarification is helpful for data plane and > > control plane communication using rte_ring. > > > > Signed-off-by: Honnappa Nagarahalli > > Reviewed-by: Gavin Hu > > Reviewed-by: Ola Liljedahl > > Acked-by: Olivier Matz Applied, thanks