From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Ilya Maximets <i.maximets@ovn.org>, dev@dpdk.org
Cc: Flavio Leitner <fbl@sysclose.org>,
David Marchand <david.marchand@redhat.com>,
Tiwei Bie <tiwei.bie@intel.com>
Subject: Re: [dpdk-dev] [PATCH] vhost: disable host TSO for linear buffers without extbuf
Date: Thu, 24 Oct 2019 11:38:52 +0200 [thread overview]
Message-ID: <eeacc445-7ef9-2878-b415-e6cb6b571e7c@redhat.com> (raw)
In-Reply-To: <20191017150019.19191-1-i.maximets@ovn.org>
On 10/17/19 5:00 PM, Ilya Maximets wrote:
> If linear buffers requested and external buffers are not, vhost
> will not be able to receive any buffer that doesn't fit in a
> single mbuf. Moreover, if such a buffer will appear in a vring
> it will never be dequeued and the whole vring will become dead
> breaking the network connection.
>
> Disable segmentation offloading from the host side to avoid
> having such a big buffers.
>
> Cc: Flavio Leitner <fbl@sysclose.org>
>
> Fixes: 5005bcda7123 ("vhost: add support for large buffers")
> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
> ---
>
> There is still an assumption that users are sane enough to have
> MTU sized mbufs in a memory pool and that guest will not change
> MTU to higher values.
>
> We, probably, still need to have a check on dequeue path and
> drop oversized buffers in case of linear buffers to avoid stuck
> of the virtqueue. Or simply drop support of '+linear -extbuf'
> case.
>
> Note: Only compile tested due to lack of HW.
>
> lib/librte_vhost/socket.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2019-10-24 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 15:00 Ilya Maximets
2019-10-24 9:38 ` Maxime Coquelin [this message]
2019-10-24 10:18 ` Maxime Coquelin
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=eeacc445-7ef9-2878-b415-e6cb6b571e7c@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fbl@sysclose.org \
--cc=i.maximets@ovn.org \
--cc=tiwei.bie@intel.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).