From: Raslan Darawsheh <rasland@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: adjust inline setting for large Tx queue sizes
Date: Tue, 8 Oct 2019 09:33:30 +0000 [thread overview]
Message-ID: <DB3PR0502MB39645D6E937E3B78A1CAABD3C29A0@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1569912817-25331-1-git-send-email-viacheslavo@mellanox.com>
Hi,
> -----Original Message-----
> From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> Sent: Tuesday, October 1, 2019 9:54 AM
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@mellanox.com>; Matan Azrad
> <matan@mellanox.com>
> Subject: [PATCH v2] net/mlx5: adjust inline setting for large Tx queue sizes
>
> The hardware may have limitations on maximal amount of supported Tx
> descriptors building blocks (WQEBB). Application requires the Tx queue must
> accept the specified amount of packets.
> If inline data feature is engaged the packet may require more WQEBBs and
> overall amount of blocks may exceed the hardware capabilities.
> Application has to make a trade-off between Tx queue size and maximal data
> inline size.
>
> In case if the inline settings are not requested explicitly with devarg keys the
> default values are used. This patch adjusts the applied default values if large
> Tx queue size is requested and default inline settings can not be satisfied due
> to hardware limitations.
>
> The explicitly requested inline setting may be aligned (enlarging
> only) by configurations routines to provide better WQEBB filling, this implicit
> alignment is the subject for adjustment either.
>
> The warning message is emitted to the log if adjustment happens.
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
>
> ---
> v2: - check explicitly specified parameters
> - allow adjust aligned parameters
> - added extra asserts
> v1:
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpatch
> es.dpdk.org%2Fpatch%2F59735%2F&data=02%7C01%7Crasland%40mell
> anox.com%7Ca35d54a2949143d3d89608d7463c25a7%7Ca652971c7d2e4d9ba6
> a4d149256f461b%7C0%7C1%7C637055096469653065&sdata=%2FCXfd2V
> VjpGntk%2BAynInVj2VQld%2BBC%2BJc66%2Bgu63hso%3D&reserved=
> 0
>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2019-10-08 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 6:53 Viacheslav Ovsiienko
2019-10-08 9:33 ` Raslan Darawsheh [this message]
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=DB3PR0502MB39645D6E937E3B78A1CAABD3C29A0@DB3PR0502MB3964.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=viacheslavo@mellanox.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).