From: Kevin Laatz <kevin.laatz@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>, <dev@dpdk.org>
Cc: <stable@dpdk.org>
Subject: Re: [PATCH 2/3] dma/idxd: configure max batch size to high value
Date: Thu, 17 Feb 2022 17:48:52 +0000 [thread overview]
Message-ID: <e733835a-dc6d-94cb-39bd-c243216423d0@intel.com> (raw)
In-Reply-To: <20220216160610.475242-3-bruce.richardson@intel.com>
On 16/02/2022 16:06, Bruce Richardson wrote:
> When configuring an Intel DSA instance using the utility script
> dpdk_idxd_cfg.py, explicitly set the max supported batch size value to a
> high value, to ensure large bursts are supported if so desired. The
> default in the linux kernel is now just 32 [1], which may not be
> sufficient for all DPDK apps.
>
> [1] https://lore.kernel.org/r/163528473483.3926048.7950067926287180976.stgit@djiang5-desk3.ch.intel.com
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> Note: although not fixing a bug in DPDK itself, due to kernel changes
> this patch should be considered for backport as a fix, so cc'ing stable.
> ---
> drivers/dma/idxd/dpdk_idxd_cfg.py | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Kevin Laatz <kevin.laatz@intel.com>
next prev parent reply other threads:[~2022-02-17 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 16:06 [PATCH 0/3] idxd driver update fixes Bruce Richardson
2022-02-16 16:06 ` [PATCH 1/3] app/test: fix missing checks for DMA device capacity Bruce Richardson
2022-02-17 12:02 ` Walsh, Conor
2022-02-17 17:48 ` Kevin Laatz
2022-02-16 16:06 ` [PATCH 2/3] dma/idxd: configure max batch size to high value Bruce Richardson
2022-02-17 17:48 ` Kevin Laatz [this message]
2022-02-16 16:06 ` [PATCH 3/3] doc/dmadev/idxd: improve configuration examples Bruce Richardson
2022-02-17 17:48 ` Kevin Laatz
2022-02-23 15:48 ` [PATCH 0/3] idxd driver update fixes 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=e733835a-dc6d-94cb-39bd-c243216423d0@intel.com \
--to=kevin.laatz@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).