From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Christophe Fontaine <cfontain@redhat.com>, chenbo.xia@intel.com
Cc: dev@dpdk.org, Christophe Fontaine <christophefontaine@mac.com>
Subject: Re: [PATCH v2 1/1] vhost: move fds outside of VhostUserMessage
Date: Tue, 8 Feb 2022 12:12:34 +0100 [thread overview]
Message-ID: <c46d5d24-b511-3ff8-18fe-e3961769d5de@redhat.com> (raw)
In-Reply-To: <20220207102129.59170-2-cfontain@redhat.com>
On 2/7/22 11:21, Christophe Fontaine wrote:
> From: Christophe Fontaine <christophefontaine@mac.com>
>
> FDs at the end of the VhostUserMessage structure limits the size
> of the payload. Move them to an other englobing structure, before
> the header & payload of a VhostUserMessage.
> Also removes a reference to fds in the VHUMsg structure defined in
> drivers/net/virtio/virtio_user/vhost_user.c
>
> Signed-off-by: Christophe Fontaine <cfontain@redhat.com>
> ---
> drivers/net/virtio/virtio_user/vhost_user.c | 1 -
> lib/vhost/vhost_crypto.c | 10 +-
> lib/vhost/vhost_user.c | 534 ++++++++++----------
> lib/vhost/vhost_user.h | 7 +-
> 4 files changed, 290 insertions(+), 262 deletions(-)
>
Applied to dpdk-next-virtio/main.
Thanks,
Maxime
prev parent reply other threads:[~2022-02-08 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 11:59 [PATCH 0/1] Removes FDs from VhostUserMessage structure Christophe Fontaine
2022-01-23 11:59 ` [PATCH 1/1] vhost: Move fds outside of VhostUserMessage Christophe Fontaine
2022-02-01 9:56 ` Maxime Coquelin
2022-02-04 12:21 ` Maxime Coquelin
2022-02-07 10:21 ` [PATCH v2 0/1] Removes FDs from VhostUserMessage structure Christophe Fontaine
2022-02-07 10:21 ` [PATCH v2 1/1] vhost: move fds outside of VhostUserMessage Christophe Fontaine
2022-02-08 9:48 ` Maxime Coquelin
2022-02-08 9:59 ` David Marchand
2022-02-08 11:12 ` 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=c46d5d24-b511-3ff8-18fe-e3961769d5de@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=cfontain@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=christophefontaine@mac.com \
--cc=dev@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).