From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbo.xia@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Shahaf Shuler <shahafs@mellanox.com>
Cc: dev@dpdk.org, Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/virtio: fix Rx scatter offload
Date: Mon, 19 Jul 2021 22:38:28 +0300 [thread overview]
Message-ID: <a79503a1-0c8a-e294-029c-590b7f689433@oktetlabs.ru> (raw)
In-Reply-To: <20210719191517.952999-1-andrew.rybchenko@oktetlabs.ru>
On 7/19/21 10:15 PM, Andrew Rybchenko wrote:
> From: Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>
>
> Report Rx scatter offload capability depending on VIRTIO_NET_F_MRG_RXBUF.
>
> If Rx scatter is not requested, ensure that provided Rx buffers on
> each Rx queue are big enough to fit Rx packets up to configured MTU.
>
> Fixes: ce17eddefc20 ("ethdev: introduce Rx queue offloads API")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>
> Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Sorry, self NACK. The patch has problem with MTU set when not all
queues are setup. Will send v3 tomorrow.
next prev parent reply other threads:[~2021-07-19 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 14:14 [dpdk-dev] [PATCH] " Andrew Rybchenko
2021-07-13 9:27 ` Maxime Coquelin
2021-07-19 19:15 ` [dpdk-dev] [PATCH v2] " Andrew Rybchenko
2021-07-19 19:38 ` Andrew Rybchenko [this message]
2021-07-20 7:54 ` [dpdk-dev] [PATCH v3] " Andrew Rybchenko
2021-07-20 16:19 ` Maxime Coquelin
2021-07-21 9:29 ` Andrew Rybchenko
2021-07-22 7:37 ` Maxime Coquelin
2021-07-21 6:17 ` Xia, Chenbo
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=a79503a1-0c8a-e294-029c-590b7f689433@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=arybchenko@solarflare.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=ivan.ilchenko@oktetlabs.ru \
--cc=konstantin.ananyev@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=shahafs@mellanox.com \
--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).