From: Piotr <p@tcy.pl>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, sarosh.arif@emumba.com, m.bilal@emumba.com
Subject: Re: [dpdk-dev] [PATCH] dpdk-setup.sh: Prevent infinite loop, when end of input.
Date: Sun, 24 May 2020 20:01:11 +0200 [thread overview]
Message-ID: <cf1a73ee-77fb-27cd-2efa-89faef82fe32@tcy.pl> (raw)
In-Reply-To: <2085526.rGYoCdkRXg@thomas>
Hi
The script dpdk-setup.sh was froze wit full cpu usage when EOF input.
For example:
dpdk-setup.sh <<< '11'
or
dpdk-setup.sh <<EOF
11
EOF
Regards
Piotr
On 2020-05-24 7:07 p.m., Thomas Monjalon wrote:
> 30/03/2020 16:18, Piotr Sieduszewski:
>> From: Piotr Sieduszewski <piotr.sieduszewski@intel.com>
>>
>> Signed-off-by: Piotr Sieduszewski <piotr.sieduszewski@intel.com>
> Please add some explanations, it may help getting reviews.
> Thanks
>
>
next prev parent reply other threads:[~2020-05-25 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 14:18 Piotr Sieduszewski
2020-05-24 17:07 ` Thomas Monjalon
2020-05-24 18:01 ` Piotr [this message]
2020-05-25 5:29 ` Sieduszewski, Piotr
2020-05-25 6:55 ` Thomas Monjalon
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=cf1a73ee-77fb-27cd-2efa-89faef82fe32@tcy.pl \
--to=p@tcy.pl \
--cc=dev@dpdk.org \
--cc=m.bilal@emumba.com \
--cc=piotr.sieduszewski@intel.com \
--cc=sarosh.arif@emumba.com \
--cc=thomas@monjalon.net \
/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).