DPDK patches and discussions
 help / color / mirror / Atom feed
From: Keiichi Watanabe <keiichiw@chromium.org>
To: dev@dpdk.org
Cc: dgreid@chromium.org, chirantan@chromium.org,
	Keiichi Watanabe <keiichiw@chromium.org>
Subject: [dpdk-dev] [PATCH v2 0/2] vhost: Add API to get negotiated protocol features
Date: Mon, 22 Mar 2021 16:22:55 +0900	[thread overview]
Message-ID: <20210322072257.2017227-1-keiichiw@chromium.org> (raw)

This patchset adds an API to get negotiated vhost protocol features in
librte_vhost so we can use it to check if an optional feature is enabled.

v1: https://mails.dpdk.org/archives/dev/2021-February/199044.html

Keiichi Watanabe (2):
  vhost: Add API to get negotiated protocol features
  examples/vhost_blk: Check protocol features before getting inflight
    info

 examples/vhost_blk/vhost_blk.c | 23 ++++++++++++++++++-----
 lib/librte_vhost/rte_vhost.h   | 15 +++++++++++++++
 lib/librte_vhost/version.map   |  1 +
 lib/librte_vhost/vhost.c       | 14 ++++++++++++++
 4 files changed, 48 insertions(+), 5 deletions(-)

--
2.31.0.rc2.261.g7f71774620-goog

             reply	other threads:[~2021-03-22  7:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22  7:22 Keiichi Watanabe [this message]
2021-03-22  7:22 ` [dpdk-dev] [PATCH v2 1/2] " Keiichi Watanabe
2021-03-25 14:16   ` Maxime Coquelin
2021-03-31 16:45   ` Ferruh Yigit
2021-04-01  8:42     ` Kinsella, Ray
2021-04-01 16:05       ` Keiichi Watanabe
2021-04-01 16:28         ` Ferruh Yigit
2021-04-01 16:38           ` Keiichi Watanabe
2021-03-22  7:22 ` [dpdk-dev] [PATCH v2 2/2] examples/vhost_blk: Check protocol features before getting inflight info Keiichi Watanabe
2021-03-25 14:18   ` Maxime Coquelin
2021-03-31  6:45 ` [dpdk-dev] [PATCH v2 0/2] vhost: Add API to get negotiated protocol features Xia, Chenbo

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=20210322072257.2017227-1-keiichiw@chromium.org \
    --to=keiichiw@chromium.org \
    --cc=chirantan@chromium.org \
    --cc=dev@dpdk.org \
    --cc=dgreid@chromium.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).