From: Bruce Richardson <bruce.richardson@intel.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] raw/ioat: fix termination descriptor for batch
Date: Fri, 16 Jul 2021 15:27:44 +0100 [thread overview]
Message-ID: <YPGXYKlVoEa+VJ2D@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20210716135027.30855-1-konstantin.ananyev@intel.com>
On Fri, Jul 16, 2021 at 02:50:27PM +0100, Konstantin Ananyev wrote:
> When batch_size == 1, idxd has to add a dummy termination descriptor
> to satisfy HW requirements.
> Right now it uses NOP descriptor with FENCE flag.
> This is excessive and fencing can slowdown things quite significantly.
> The patch removes FENCE flag from termination dummy descriptor.
> That helps to improve performance for no-burst scenarios.
>
> Fixes: 245efe544d8e ("raw/ioat: report status of completed jobs")
>
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Thanks for patch.
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2021-07-16 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 13:50 Konstantin Ananyev
2021-07-16 14:27 ` Bruce Richardson [this message]
2021-07-20 13:51 ` David Marchand
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=YPGXYKlVoEa+VJ2D@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@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).