From: Thomas Monjalon <thomas@monjalon.net>
To: Alexander Kozyrev <akozyrev@mellanox.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Cc: dev@dpdk.org, rasland@mellanox.com, matan@mellanox.com,
viacheslavo@mellanox.com, stable@dpdk.org,
David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v4 1/3] net/mlx5: add a devarg to specify MPRQ stride size
Date: Tue, 14 Apr 2020 14:52:38 +0200 [thread overview]
Message-ID: <3469922.C4sosBPzcN@thomas> (raw)
In-Reply-To: <9093c839-5655-6583-cc10-471a51ecccca@intel.com>
14/04/2020 13:42, Ferruh Yigit:
> On 4/9/2020 11:23 PM, Alexander Kozyrev wrote:
> > Define a device parameter to configure log 2 of a stride size for MPRQ
> > - mprq_log_stride_size. User is able to specify a stride size in a range
> > allowed by an underlying hardware. The default stride size is defined as
> > 2048 bytes to encompass most commonly used packet sizes in the Internet
> > (MTU 1518 and less) and will be used in case a maximum configured packet
> > size cannot fit into the largest possible stride size. Otherwise a
> > stride size is set to a large enough value to encompass a whole packet.
> >
> > Cc: stable@dpdk.org
>
> Hi Alexander,
>
> This is a new feature, and you are asking it for to be backported to the stable
> trees.
>
> There is no question on getting the fixes to the stable tree, but for
> backporting features I would like to get the comment of the stable tree
> maintainers first before merging the series.
As far as I know, there is a fix hidden in this series,
for the case of jumbo frames.
In my understanding, jumbo frames cannot be fixed without a new option.
I agree it's tricky deciding what is the limit with backports.
next prev parent reply other threads:[~2020-04-14 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1585851108-485-1-git-send-email-akozyrev@mellanox.com>
[not found] ` <1586471033-17130-1-git-send-email-akozyrev@mellanox.com>
2020-04-09 22:23 ` [dpdk-stable] " Alexander Kozyrev
2020-04-14 11:42 ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit
2020-04-14 12:52 ` Thomas Monjalon [this message]
2020-04-15 11:01 ` Ferruh Yigit
2020-04-15 11:25 ` Luca Boccassi
2020-04-15 15:34 ` Alexander Kozyrev
2020-04-15 15:52 ` Luca Boccassi
2020-04-09 22:23 ` [dpdk-stable] [PATCH v4 2/3] net/mlx5: enable MPRQ multi-stride operations Alexander Kozyrev
2020-04-09 22:23 ` [dpdk-stable] [PATCH v4 3/3] net/mlx5: add multi-segment packets in MPRQ mode Alexander Kozyrev
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=3469922.C4sosBPzcN@thomas \
--to=thomas@monjalon.net \
--cc=akozyrev@mellanox.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=matan@mellanox.com \
--cc=rasland@mellanox.com \
--cc=stable@dpdk.org \
--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).