DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "Stokes, Ian" <ian.stokes@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
	 Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	"Akhil, Goyal" <akhil.goyal@nxp.com>,
	 "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
	"Xu, Qian Q" <qian.q.xu@intel.com>,
	 Yongseok Koh <yskoh@mellanox.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	 "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	 "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 23/5/2019
Date: Thu, 23 May 2019 15:55:06 +0200	[thread overview]
Message-ID: <CAJFAV8xdin+SiKsmOEXpEh7ryeA-iagYS4j5a_Wmy5fAmJGAtw@mail.gmail.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23F642A3F@IRSMSX103.ger.corp.intel.com>

On Thu, May 23, 2019 at 1:47 PM Mcnamara, John <john.mcnamara@intel.com>
wrote:

> Minutes 23 May 2019
> -------------------
>
>
[snip]

OvS
> ---
>
> * 18.11.2 RC1 is out.
> * Need to look at the impact of the rte_prefix.
>

It has an impact on OvS (checked with dpdk-latest) even if the fix should
be not that difficult and concentrated on lib/netdev-dpdk.c.


-- 
David Marchand

      reply	other threads:[~2019-05-23 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 11:46 Mcnamara, John
2019-05-23 13:55 ` 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=CAJFAV8xdin+SiKsmOEXpEh7ryeA-iagYS4j5a_Wmy5fAmJGAtw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=akhil.goyal@nxp.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=ian.stokes@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=john.mcnamara@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=yskoh@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).