From: "Laatz, Kevin" <kevin.laatz@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Hu, Jiayu" <jiayu.hu@intel.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] raw/ioat: remove special case for no status reporting
Date: Wed, 12 May 2021 16:11:53 +0000 [thread overview]
Message-ID: <SJ0PR11MB505563D486615B94E6A53F38FC529@SJ0PR11MB5055.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210512145000.249215-2-bruce.richardson@intel.com>
> The special fast-path for returning completed descriptors without
> reporting status or user-handles returns the number of completed ring
> slots used, rather than the number of actual user-submitted jobs. This
> means that the counts returned are too high, as the batch descriptor
> slots would be included in the total. Therefore remove this special
> case, and use the normal status-processing path so that the returned
> count is correct in all cases.
>
> Fixes: 245efe544d8e ("raw/ioat: report status of completed jobs")
>
> Reported-by: Jiayu Hu <jiayu.hu@intel.com>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
<...>
Acked-by: Kevin Laatz <kevin.laatz@intel.com>
next prev parent reply other threads:[~2021-05-12 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 14:49 [dpdk-dev] [PATCH 1/2] raw/ioat: fix ring space checks Bruce Richardson
2021-05-12 14:50 ` [dpdk-dev] [PATCH 2/2] raw/ioat: remove special case for no status reporting Bruce Richardson
2021-05-12 16:11 ` Laatz, Kevin [this message]
2021-05-12 18:49 ` Thomas Monjalon
2021-05-12 16:11 ` [dpdk-dev] [PATCH 1/2] raw/ioat: fix ring space checks Laatz, Kevin
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=SJ0PR11MB505563D486615B94E6A53F38FC529@SJ0PR11MB5055.namprd11.prod.outlook.com \
--to=kevin.laatz@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@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).