From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: arie abergel <arieabergel@hotmail.fr>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: Question about RTE ring
Date: Thu, 11 Apr 2024 09:24:58 +0000 [thread overview]
Message-ID: <7e7f1b58322945f8bb0188ea6bd2e093@huawei.com> (raw)
In-Reply-To: <HE1P195MB007380B714F3F6D211AC381FDF052@HE1P195MB0073.EURP195.PROD.OUTLOOK.COM>
>
> Thans for your response !
>
> Yes, using rte_ring between multiple process.
>
> So in this case you’re saying the behavior is undefined ?
> In my case another process crashed after that.
Without a proper debug session it is really hard to tell what is going on.
If the situation is reproducible, I'd suggest to run it with gdb and see.
>
> > Le 11 avr. 2024 à 11:08, Konstantin Ananyev <konstantin.ananyev@huawei.com> a écrit :
> >
> >
> >
> > Hi,
> >>
> >> As part of a project I have a question about the rte ring.
> >> I’m using rte ring multi producer/single consumer.
> >> The producers are several process.
> >> If one producer is enqueuing an element and crashed (kill pid) in the middle of the
> >> enqueuing, can it compromise the ring ?
> >
> > I suppose you are using rte_ring as IPC mechanism between multiple processes, correct?
> > In theory - yes, if your producer crashed during enqueue() to the ring, then yes, the ring might be affected.
> > If producer already moved prod.head and crashed before updating prod.tail, then no other producers
> > will be able to enqueue() into the ring, till you'll do reset() for it.
> > I expect such situation really rare and hard to reproduce, but in theory it is possible.
> > Konstantin
prev parent reply other threads:[~2024-04-11 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 10:56 arie abergel
2024-04-11 8:08 ` Konstantin Ananyev
2024-04-11 8:34 ` arie abergel
2024-04-11 9:24 ` Konstantin Ananyev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e7f1b58322945f8bb0188ea6bd2e093@huawei.com \
--to=konstantin.ananyev@huawei.com \
--cc=arieabergel@hotmail.fr \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).