From: Shahaf Shuler <shahafs@mellanox.com>
To: Matan Azrad <matan@mellanox.com>,
Mordechay Haimovsky <motih@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx4: advertise jumbo frame support in Rx
Date: Wed, 1 Aug 2018 12:51:47 +0000 [thread overview]
Message-ID: <DB7PR05MB44260E2DC47E1CF4A74084F4C32D0@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <VI1PR0501MB2608AF92D2834FC2BAD79327D22D0@VI1PR0501MB2608.eurprd05.prod.outlook.com>
Wednesday, August 1, 2018 1:15 PM, Matan Azrad:
> Subject: Re: [dpdk-dev] [PATCH] net/mlx4: advertise jumbo frame support in
> Rx
>
> Hi Moti
>
> From: Mordechay Haimovsky
> > This commit adds the missing Rx jumbo frame support advertisement in
> > Rx offload capabilities.
> >
> > Signed-off-by: Moti Haimovsky <motih@mellanox.com>
> > ---
> > drivers/net/mlx4/mlx4_rxq.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/mlx4/mlx4_rxq.c b/drivers/net/mlx4/mlx4_rxq.c
> > index
> > e8bef1d..9737da2 100644
> > --- a/drivers/net/mlx4/mlx4_rxq.c
> > +++ b/drivers/net/mlx4/mlx4_rxq.c
> > @@ -679,7 +679,8 @@ struct mlx4_rss *
> > {
> > uint64_t offloads = DEV_RX_OFFLOAD_SCATTER |
> > DEV_RX_OFFLOAD_CRC_STRIP |
> > - DEV_RX_OFFLOAD_KEEP_CRC;
> > + DEV_RX_OFFLOAD_KEEP_CRC |
> > + DEV_RX_OFFLOAD_JUMBO_FRAME;
> >
> > if (priv->hw_csum)
> > offloads |= DEV_RX_OFFLOAD_CHECKSUM;
> > --
>
> This patch should be backported to the stable branch.
>
> Shahaf, can you add cc stable in the integration?
>
> Cc: stable@dpdk.org
>
> Acked-by: Matan Azrad <matan@mellanox.com>
Applied to next-net-mlx with Cc'ing stable. Thanks.
>
prev parent reply other threads:[~2018-08-01 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 16:13 Moti Haimovsky
2018-08-01 10:14 ` Matan Azrad
2018-08-01 12:51 ` Shahaf Shuler [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=DB7PR05MB44260E2DC47E1CF4A74084F4C32D0@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=motih@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).