From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Igor Romanov <igor.romanov@oktetlabs.ru>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] app/testpmd: fix stdout flush absence after printing stats
Date: Wed, 20 Mar 2019 20:13:29 +0000 [thread overview]
Message-ID: <08204589-8edf-01fd-73f1-92415a863ca8@intel.com> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260D73800@IRSMSX108.ger.corp.intel.com>
On 3/20/2019 1:21 PM, Iremonger, Bernard wrote:
> Hi Andrew,
>
>> -----Original Message-----
>> From: Andrew Rybchenko [mailto:arybchenko@solarflare.com]
>> Sent: Monday, March 18, 2019 11:36 AM
>> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu, Jingjing
>> <jingjing.wu@intel.com>; Iremonger, Bernard
>> <bernard.iremonger@intel.com>
>> Cc: dev@dpdk.org; Igor Romanov <igor.romanov@oktetlabs.ru>;
>> stable@dpdk.org
>> Subject: [PATCH] app/testpmd: fix stdout flush absence after printing stats
>>
>> From: Igor Romanov <igor.romanov@oktetlabs.ru>
>>
>> User can specify stats period(n). The statistics should be available to user
>> every n second. But the print_stats() function does not force stdout to be
>> flushed, so for instance, a user reading testpmd's stdout through pipe will
>> not be able to read it untill the stdout buffer is filled.
>>
>> Fixes: cfea1f3048d1 ("app/testpmd: print statistics periodically")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Igor Romanov <igor.romanov@oktetlabs.ru>
>> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
>
> There is a checkpatch warning on the commit messge.
> WARNING:TYPO_SPELLING: 'untill' may be misspelled - perhaps 'until'?
>
> Otherwise
>
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com
>
Applied to dpdk-next-net/master, thanks.
(warning fixed while merging)
next prev parent reply other threads:[~2019-03-20 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 11:35 [dpdk-dev] " Andrew Rybchenko
2019-03-18 11:35 ` Andrew Rybchenko
2019-03-20 13:21 ` Iremonger, Bernard
2019-03-20 13:21 ` Iremonger, Bernard
2019-03-20 20:13 ` Ferruh Yigit [this message]
2019-03-20 20:13 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
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=08204589-8edf-01fd-73f1-92415a863ca8@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=igor.romanov@oktetlabs.ru \
--cc=jingjing.wu@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.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).