DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: web@dpdk.org, ferruh.yigit@intel.com, ajit.khaparde@broadcom.com,
	qi.z.zhang@intel.com, jerinj@marvell.com, rasland@mellanox.com,
	maxime.coquelin@redhat.com, akhil.goyal@nxp.com
Subject: Re: [dpdk-web] [RFC PATCH] prepare 20.11 roadmap
Date: Sun, 09 Aug 2020 00:10:07 +0200	[thread overview]
Message-ID: <5830353.hxtrKpkrUE@thomas> (raw)
In-Reply-To: <20200804095846.8964-1-david.marchand@redhat.com>

04/08/2020 11:58, David Marchand:
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> Hello tree maintainers,
> 
> I prepared this roadmap update based on the 20.08 release notes and my
> understanding of the changes that happened in the drivers.
> I moved to 20.11 the features still in progress or for which I did not
> find changes.
> Please chime in if you think there are still things to do wrt the
> previously announced features.
> 
> Thanks!
> 
[...]
> -- performance optimizations in mlx drivers for Arm platforms

Arm C11 optimization was not merged.

>  - mlx5 memory management options, and queue stop/start

These ones are completed.

> -- mlx5 eCPRI matching and Tx scheduling for 5G
> -- mlx5 vDPA device counters
> -- octeontx2 parameters for Rx/Tx context locking
>  - octeontx2 packet mirroring
> +- octeontx2 rte_tm enhancement
>  - qede SR-IOV PF
>  <!-- Virtualisation -->
> -- vhost async API
> -- vhost DMA operations with CBDMA ioat driver

According to Maxime, we should keep this item for 20.11.

> -- vhost REPLY_ACK advertised unconditionally
> -- vhost SET_STATUS
>  - virtio-user GET/SET_PROTOCOL_FEATURES, REPLY_ACK, SET_STATUS

Thanks for preparing



      parent reply	other threads:[~2020-08-08 22:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  9:58 David Marchand
2020-08-04 10:03 ` Maxime Coquelin
2020-08-08 21:58   ` Thomas Monjalon
2020-08-09 11:17     ` Fu, Patrick
2020-08-08 22:10 ` Thomas Monjalon [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=5830353.hxtrKpkrUE@thomas \
    --to=thomas@monjalon.net \
    --cc=ajit.khaparde@broadcom.com \
    --cc=akhil.goyal@nxp.com \
    --cc=david.marchand@redhat.com \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rasland@mellanox.com \
    --cc=web@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).