From: Fuji Nafiul <nafiul.fuji@gmail.com>
To: users@dpdk.org
Subject: how to make dpdk processes tolerable to segmantation fault?
Date: Thu, 30 Nov 2023 13:45:45 +0600 [thread overview]
Message-ID: <CA+3hWewYyGATrD32OodkPNtoQCNiEvQX6DXvJiW_=xs6EXLVCQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
In a normal c program, I saw that the segmentation fault in 1 loosely
coupled thread doesn't necessarily affect other threads or the main
program. There, I can check all the threads by process ID of it in every
certain period of time and if some unexepected segmentation fault occurs or
got killed I can re run the thread and it works fine. I can later monitor
the logs and inspect the situation.
But I saw that, segmentation fault or other unexpected error in remotely
launched (using DPDK) functions on different core affects the whole dpdk
process and whole dpdk program crashes.. why is that?
Is there any alternative way to handle this scenario ? How can I take
measures for unexpected future error occurance where I should auto rerun
dpdk remote processes in live system?
[-- Attachment #2: Type: text/html, Size: 827 bytes --]
next reply other threads:[~2023-11-30 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 7:45 Fuji Nafiul [this message]
2023-11-30 16:24 ` Dmitry Kozlyuk
2023-11-30 21:19 ` Stephen Hemminger
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='CA+3hWewYyGATrD32OodkPNtoQCNiEvQX6DXvJiW_=xs6EXLVCQ@mail.gmail.com' \
--to=nafiul.fuji@gmail.com \
--cc=users@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).