DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, i.maximets@samsung.com, changpeng.liu@intel.com,
	tiwei.bie@intel.com, dariusz.stojaczyk@intel.com
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-dev] [PATCH v3 0/2] vhost: Support external backend only vhost-user requests
Date: Tue, 19 Mar 2019 11:54:15 +0100	[thread overview]
Message-ID: <20190319105417.16890-1-maxime.coquelin@redhat.com> (raw)

The goals of this series is to provide more flexibility to external
backends to implement their specific vhost-user request handling
without having to patch vhost-user library.

First patch implements a new API for external backend to advertize
its specific protocol features to vhost-user master.

Second patch ensures a request not handled by the vhost-user library
but by the external backend only will not be treated as an error or
make the vhost lib to crash.

Changes in v3:
==============
 - Fix and improve comments (Ilya)

Changes in v2:
==============
 - Remove 'skip_master' param from documentation (Ilya)
 - Merge pre and post callback in a single one (Ilya)

Changes in v1:
==============
 - Convert vhost-crypto to the API change (Ilya)
 - Fix build with recent GCC (fall-through)
 - Check request > VHOST_USER_NONE (Ilya)
 - Remove 'Requested invalid message type' check (Ilya)

Changes in RFC v2:
==================
 - Fix build & git message
 - Add new enum for not handled messages & remove skip_master (Ilya)

Maxime Coquelin (2):
  vhost: add API to set protocol features flags
  vhost: support requests only handled by external backend

 lib/librte_vhost/rte_vhost.h           | 53 +++++++++--------
 lib/librte_vhost/rte_vhost_version.map |  1 +
 lib/librte_vhost/socket.c              | 14 +++++
 lib/librte_vhost/vhost_crypto.c        | 10 +++-
 lib/librte_vhost/vhost_user.c          | 82 ++++++++++++++++----------
 5 files changed, 102 insertions(+), 58 deletions(-)

-- 
2.20.1

             reply	other threads:[~2019-03-19 10:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 10:54 Maxime Coquelin [this message]
2019-03-19 10:54 ` Maxime Coquelin
2019-03-19 10:54 ` [dpdk-dev] [PATCH v3 1/2] vhost: add API to set protocol features flags Maxime Coquelin
2019-03-19 10:54   ` Maxime Coquelin
2019-03-19 10:54 ` [dpdk-dev] [PATCH v3 2/2] vhost: support requests only handled by external backend Maxime Coquelin
2019-03-19 10:54   ` Maxime Coquelin
2019-03-20  4:54   ` Tiwei Bie
2019-03-20  4:54     ` Tiwei Bie
2019-03-20  7:34 ` [dpdk-dev] [PATCH v3 0/2] vhost: Support external backend only vhost-user requests Maxime Coquelin
2019-03-20  7:34   ` Maxime Coquelin
2019-03-20 14:32   ` Stojaczyk, Dariusz
2019-03-20 14:32     ` Stojaczyk, Dariusz
2019-03-21  9:21     ` Maxime Coquelin
2019-03-21  9:21       ` Maxime Coquelin
2019-03-22 10:29       ` Zhang, Roy Fan
2019-03-22 10:29         ` Zhang, Roy Fan

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=20190319105417.16890-1-maxime.coquelin@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=changpeng.liu@intel.com \
    --cc=dariusz.stojaczyk@intel.com \
    --cc=dev@dpdk.org \
    --cc=i.maximets@samsung.com \
    --cc=tiwei.bie@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).