DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: xuan.ding@intel.com, chenbo.xia@intel.com
Cc: dev@dpdk.org, jiayu.hu@intel.com, cheng1.jiang@intel.com,
	sunil.pai.g@intel.com
Subject: Re: [PATCH v1 0/2] vhost: add unsafe API to get DMA inflight packets
Date: Thu, 5 May 2022 21:55:42 +0200	[thread overview]
Message-ID: <684072c9-fe3c-ee25-cd58-3585d1615737@redhat.com> (raw)
In-Reply-To: <20220408102214.11994-1-xuan.ding@intel.com>



On 4/8/22 12:22, xuan.ding@intel.com wrote:
 > This patchset introduces an unsafe API to get the number of inflight
 > packets in DMA engine. It should be only used within the vhost ops
 > which already holds the lock. Like vring state changes or device is
 > destroyed. Compared with rte_vhost_async_get_inflight(), this is a
 > lock free version.
 >
 > RFC v1->v1:
 > * refine the doc and commit log
 >
 > Xuan Ding (2):
 >   vhost: add unsafe API to check inflight packets
 >   examples/vhost: use API to check inflight packets
 >
 >  doc/guides/prog_guide/vhost_lib.rst    |  6 ++++++
 >  doc/guides/rel_notes/release_22_07.rst |  4 ++++
 >  examples/vhost/main.c                  | 28 ++++++++++++++------------
 >  examples/vhost/main.h                  |  1 -
 >  lib/vhost/rte_vhost_async.h            | 17 ++++++++++++++++
 >  lib/vhost/version.map                  |  4 ++++
 >  lib/vhost/vhost.c                      | 26 ++++++++++++++++++++++++
 >  7 files changed, 72 insertions(+), 14 deletions(-)


Applied to dpdk-next-virtio/main.

Thanks,
Maxime


      parent reply	other threads:[~2022-05-05 19:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 10:22 xuan.ding
2022-04-08 10:22 ` [PATCH v1 1/2] vhost: add unsafe API to check " xuan.ding
2022-05-05 19:21   ` Maxime Coquelin
2022-05-06  1:45     ` Ding, Xuan
2022-04-08 10:22 ` [PATCH v1 2/2] examples/vhost: use " xuan.ding
2022-05-05 19:55 ` Maxime Coquelin [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=684072c9-fe3c-ee25-cd58-3585d1615737@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=cheng1.jiang@intel.com \
    --cc=dev@dpdk.org \
    --cc=jiayu.hu@intel.com \
    --cc=sunil.pai.g@intel.com \
    --cc=xuan.ding@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).