From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 26/9/2019
Date: Thu, 26 Sep 2019 15:05:40 +0200 [thread overview]
Message-ID: <CAJFAV8yazN6ZOW93bwh1fUMj_miCYx8F6BvaYmnxOo3eT1L84Q@mail.gmail.com> (raw)
In-Reply-To: <0d21509e-2d74-86aa-0b33-c557df41daf3@intel.com>
On Thu, Sep 26, 2019 at 2:52 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
> Minutes 26 September 2019
> -------------------------
>
[snip]
> OvS
> ---
>
> * Intel is pushing multi-seg TSO support
> * A patch may be required in DPDK vhost side
There seems to be some confusion here.
Michal (@Intel) sent new patchsets for TSO support [1] using multiseg [2].
Flavio proposed a PoC as an alternative solution [3] but it would
require a change in the dpdk vhost library [4].
1: https://patchwork.ozlabs.org/project/openvswitch/list/?series=130206
2: https://patchwork.ozlabs.org/project/openvswitch/list/?series=130193
3: https://patchwork.ozlabs.org/project/openvswitch/list/?series=132124
4: https://patchwork.ozlabs.org/project/openvswitch/list/?series=132126
--
David Marchand
prev parent reply other threads:[~2019-09-26 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 12:52 Ferruh Yigit
2019-09-26 13:05 ` David Marchand [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=CAJFAV8yazN6ZOW93bwh1fUMj_miCYx8F6BvaYmnxOo3eT1L84Q@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
/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).