From: Thomas Monjalon <thomas@monjalon.net>
To: "Sieduszewski, Piotr" <piotr.sieduszewski@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"sarosh.arif@emumba.com" <sarosh.arif@emumba.com>,
"m.bilal@emumba.com" <m.bilal@emumba.com>
Subject: Re: [dpdk-dev] [PATCH] dpdk-setup.sh: Prevent infinite loop, when end of input.
Date: Mon, 25 May 2020 08:55:08 +0200 [thread overview]
Message-ID: <17478010.U4H6pJmV2A@thomas> (raw)
In-Reply-To: <DM6PR11MB3306FBB9A80446A9FD135BA595B30@DM6PR11MB3306.namprd11.prod.outlook.com>
25/05/2020 07:29, Sieduszewski, Piotr:
> Hi
>
> I send answer yesterday, but now I put more examples from my scripts at work:
Please send a patch v2 with more explanations in sentences.
It would be appreciated if you use --in-reply-to.
PS: please do not top-post, do not use HTML, and do not mark email as confidential.
> as first, very simple deadlock:
>
> Dpd-setup.sh < /dev/null
>
>
>
>
>
> Deadlock without patch:
>
>
>
> for NIC in ${RTE_NIC-0000:3d:00.1} ; do
>
> $RTE_SDK/usertools/dpdk-setup.sh <<< "51
>
> ${NIC}
>
>
>
> 62
>
> "
>
> Done
>
>
>
> Above works only witch additional empty line:
>
>
>
> for NIC in ${RTE_NIC-0000:3d:00.1} ; do
>
> $RTE_SDK/usertools/dpdk-setup.sh <<< "51
>
> ${NIC}
>
>
>
> 62
>
>
>
> "
>
> Done
>
>
>
>
>
> .. or other deadlock:
>
>
>
> usertools/dpdk-setup.sh <<< '41
>
>
>
> 62
>
> '
>
>
>
> usertools/dpdk-setup.sh <<< '41
>
>
>
> 62
>
>
>
> '
>
>
>
>
>
> Regards
>
>
>
> Piotr
>
>
>
>
>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: 2020 May 24 19:08
> To: Sieduszewski, Piotr <piotr.sieduszewski@intel.com>
> Cc: dev@dpdk.org; Piotr Sieduszewski <piotr@dobra.waw.pl>; sarosh.arif@emumba.com; m.bilal@emumba.com
> Subject: Re: [dpdk-dev] [PATCH] dpdk-setup.sh: Prevent infinite loop, when end of input.
>
>
>
> 30/03/2020 16:18, Piotr Sieduszewski:
>
> > From: Piotr Sieduszewski <piotr.sieduszewski@intel.com<mailto:piotr.sieduszewski@intel.com>>
>
> >
>
> > Signed-off-by: Piotr Sieduszewski <piotr.sieduszewski@intel.com<mailto:piotr.sieduszewski@intel.com>>
>
>
>
> Please add some explanations, it may help getting reviews.
>
> Thanks
>
>
>
>
> ---------------------------------------------------------------------
> Intel Technology Poland sp. z o.o.
> ul. Sowackiego 173 | 80-298 Gdask | Sd Rejonowy Gdask Pnoc | VII Wydzia Gospodarczy Krajowego Rejestru Sdowego - KRS 101882 | NIP 957-07-52-316 | Kapita zakadowy 200.000 PLN.
> Ta wiadomo wraz z zacznikami jest przeznaczona dla okrelonego adresata i moe zawiera informacje poufne. W razie przypadkowego otrzymania tej wiadomoci, prosimy o powiadomienie nadawcy oraz trwae jej usunicie; jakiekolwiek przegldanie lub rozpowszechnianie jest zabronione.
> This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.
>
>
prev parent reply other threads:[~2020-05-25 6:55 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
2020-05-25 5:29 ` Sieduszewski, Piotr
2020-05-25 6:55 ` Thomas Monjalon [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=17478010.U4H6pJmV2A@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=m.bilal@emumba.com \
--cc=piotr.sieduszewski@intel.com \
--cc=sarosh.arif@emumba.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).