From: Ferruh Yigit <ferruh.yigit@intel.com>
To: vattunuru@marvell.com, dev@dpdk.org
Cc: david.marchand@redhat.com, thomas@monjalon.net, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] [v1 1/1] examples/kni: fix SIGTERM signal handling
Date: Tue, 4 Feb 2020 13:37:14 +0000 [thread overview]
Message-ID: <19c39fdb-cb85-b31e-625b-3a4c7e29bf71@intel.com> (raw)
In-Reply-To: <20200204084214.18801-1-vattunuru@marvell.com>
On 2/4/2020 8:42 AM, vattunuru@marvell.com wrote:
> From: Vamsi Attunuru <vattunuru@marvell.com>
>
> Current KNI example application is not handling SIGTERM
> signal when application is killed without passing any
> specific signal in kill command.
>
> Patch uses the existing signal handler for SIGTERM as well
> for graceful application exit.
>
> Fixes: 13c4ebd65a77 ("examples: minor changes")
> Cc: stable@dpdk.org
Hi Vamsi,
No concern adding SIGTERM handling, although you can use 'kill' to send
supported signal (or just C-c (SIGINT)), it doesn't hurt to handle SIGTERM too
but that is not a fix.
Can you please reword to commit log to say SIGTERM handling added? Feel free to
add my ack on to it.
>
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
> ---
> examples/kni/main.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/examples/kni/main.c b/examples/kni/main.c
> index 5f713e6..29fc37e 100644
> --- a/examples/kni/main.c
> +++ b/examples/kni/main.c
> @@ -176,9 +176,13 @@ signal_handler(int signum)
> return;
> }
>
> - /* When we receive a RTMIN or SIGINT signal, stop kni processing */
> - if (signum == SIGRTMIN || signum == SIGINT){
> - printf("\nSIGRTMIN/SIGINT received. KNI processing stopping.\n");
> + /*
> + * When we receive a RTMIN or SIGINT or SIGTERM signal,
> + * stop kni processing
> + */
> + if (signum == SIGRTMIN || signum == SIGINT || signum == SIGTERM) {
> + printf("\nSIGRTMIN/SIGINT/SIGTERM received. "
> + "KNI processing stopping.\n");
> rte_atomic32_inc(&kni_stop);
> return;
> }
> @@ -1006,6 +1010,7 @@ main(int argc, char** argv)
> signal(SIGUSR2, signal_handler);
> signal(SIGRTMIN, signal_handler);
> signal(SIGINT, signal_handler);
> + signal(SIGTERM, signal_handler);
>
> /* Initialise EAL */
> ret = rte_eal_init(argc, argv);
>
next prev parent reply other threads:[~2020-02-04 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 8:42 vattunuru
2020-02-04 13:37 ` Ferruh Yigit [this message]
2020-02-06 11:53 ` [dpdk-dev] [PATCH] [v2 1/1] examples/kni: add " vattunuru
2020-02-13 17:36 ` David Marchand
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=19c39fdb-cb85-b31e-625b-3a4c7e29bf71@intel.com \
--to=ferruh.yigit@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=vattunuru@marvell.com \
/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).