From: "Yang, Zhiyong" <zhiyong.yang@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
";thomas@monjalon.net" <?thomas@monjalon.net>
Cc: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
Subject: Re: [dpdk-dev] [PATCH] l2fwd_fork: fix missing updating the prev_tsc
Date: Fri, 28 Apr 2017 09:23:54 +0000 [thread overview]
Message-ID: <E182254E98A5DA4EB1E657AC7CB9BD2A3EBA97DB@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <1487815258-58112-1-git-send-email-zhiyong.yang@intel.com>
Hi, Thomas:
The patch is always not noticed by anyone.
Could it be applied to 17.05 ? it indeed is a bug.
Thanks
Zhiyong
> -----Original Message-----
> From: Yang, Zhiyong
> Sent: Thursday, February 23, 2017 10:01 AM
> To: dev@dpdk.org
> Cc: Gonzalez Monroy, Sergio <sergio.gonzalez.monroy@intel.com>; Yang,
> Zhiyong <zhiyong.yang@intel.com>
> Subject: [PATCH] l2fwd_fork: fix missing updating the prev_tsc
>
> To miss updating the variable prev_tsc in function l2fwd_main_loop() The patch
> fixes it.
>
> Fixes:e2366e74e029("examples: use buffered Tx")
> CC: sergio.gonzalez.monroy@intel.com
>
> Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>
> ---
> examples/multi_process/l2fwd_fork/main.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/examples/multi_process/l2fwd_fork/main.c
> b/examples/multi_process/l2fwd_fork/main.c
> index 2d951d9..6052c84 100644
> --- a/examples/multi_process/l2fwd_fork/main.c
> +++ b/examples/multi_process/l2fwd_fork/main.c
> @@ -672,6 +672,8 @@ l2fwd_main_loop(void)
> port_statistics[portid].tx += sent;
>
> }
> +
> + prev_tsc = cur_tsc;
> }
>
> /*
> --
> 2.7.4
next prev parent reply other threads:[~2017-04-28 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 2:00 Zhiyong Yang
2017-04-28 9:23 ` Yang, Zhiyong [this message]
2017-05-01 14:31 ` 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=E182254E98A5DA4EB1E657AC7CB9BD2A3EBA97DB@BGSMSX101.gar.corp.intel.com \
--to=zhiyong.yang@intel.com \
--cc=?thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=sergio.gonzalez.monroy@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).