From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dmitry Vyal <dmitryvyal-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Thread preemption and rte_ring
Date: Tue, 05 Nov 2013 14:46:19 +0400
Message-ID: <5278CC7B.9040600@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
To: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Return-path: <dev-bounces-VfR2kkLFssw@public.gmane.org>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request-VfR2kkLFssw@public.gmane.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev-VfR2kkLFssw@public.gmane.org>
List-Help: <mailto:dev-request-VfR2kkLFssw@public.gmane.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request-VfR2kkLFssw@public.gmane.org?subject=subscribe>
Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org
Sender: "dev" <dev-bounces-VfR2kkLFssw@public.gmane.org>

Hello,

Documentation for rte_ring says: the ring implementation is not 
preemptable. A lcore must not be interrupted by another task that uses 
the same ring. What does it precisely mean? Must all the producers and 
consumers be non-preemptive? Can we relax that restriction somehow? Say, 
can I have multiple non-preemptive writers running on dedicated cores 
and a single reader running as a regular Linux thread?

Thanks,
Dmitry