From: Jason Wang <jasowang@redhat.com>
To: Eric Biggers <ebiggers3@gmail.com>,
linux-fsdevel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>
Cc: kvm@vger.kernel.org, "Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 0/3] vhost: simplify use of eventfds
Date: Tue, 9 Jan 2018 11:20:45 +0800 [thread overview]
Message-ID: <c498d59d-d030-73e9-b9c9-e67cfc6accd5@redhat.com> (raw)
In-Reply-To: <20180106225221.1965-1-ebiggers3@gmail.com>
On 2018年01月07日 06:52, Eric Biggers wrote:
> This series updates some of the vhost ioctls to grab a reference to just
> the eventfd_ctx instead of to both the eventfd_ctx and eventfd file,
> since only the eventfd_ctx is needed. This simplifies the code and
> eliminates all but one user of eventfd_fget().
>
> Eric Biggers (3):
> vhost: don't hold onto file pointer for VHOST_SET_VRING_CALL
> vhost: don't hold onto file pointer for VHOST_SET_VRING_ERR
> vhost: don't hold onto file pointer for VHOST_SET_LOG_FD
>
> drivers/vhost/vhost.c | 62 ++++++++++++---------------------------------------
> drivers/vhost/vhost.h | 3 ---
> 2 files changed, 14 insertions(+), 51 deletions(-)
>
Reviewed-by: Jason Wang <jasowang@redhat.com>
prev parent reply other threads:[~2018-01-09 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 22:52 [PATCH 0/3] vhost: simplify use of eventfds Eric Biggers
2018-01-06 22:52 ` [PATCH 1/3] vhost: don't hold onto file pointer for VHOST_SET_VRING_CALL Eric Biggers
2018-01-06 22:52 ` [PATCH 2/3] vhost: don't hold onto file pointer for VHOST_SET_VRING_ERR Eric Biggers
2018-01-06 22:52 ` [PATCH 3/3] vhost: don't hold onto file pointer for VHOST_SET_LOG_FD Eric Biggers
2018-01-09 3:20 ` Jason Wang [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=c498d59d-d030-73e9-b9c9-e67cfc6accd5@redhat.com \
--to=jasowang@redhat.com \
--cc=ebiggers3@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=viro@ZenIV.linux.org.uk \
/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).