mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Drivers: hv: kvp,vss: improve kernel-userspace communication in failure case
Date: Thu,  6 Nov 2014 18:21:23 +0100	[thread overview]
Message-ID: <1415294485-23945-1-git-send-email-vkuznets@redhat.com> (raw)

This series addresses two issues:
- There is no timeout when communicating with userspace VSS daemon.
- In case we fail to send a message to VSS or KVP userspace daemons we
  can report the failure to the host right away avoiding the timeout.

Newly introduced 10 second timeout is something worth discussing. In theory freeze/thaw
ioctls should be fast. In case someone thinks 10 seconds is not enough we can easily
increase it as we cover the most common failure scenario (when the daemon was stopped)
with the second patch of this series.

Vitaly Kuznetsov (2):
  Drivers: hv: vss: Introduce timeout for communication with userspace
  Drivers: hv: kvp,vss: Fast propagation of userspace communication
    failure

 drivers/hv/hv_kvp.c      |  9 ++++++++-
 drivers/hv/hv_snapshot.c | 28 +++++++++++++++++++++++++---
 2 files changed, 33 insertions(+), 4 deletions(-)

-- 
1.9.3


             reply	other threads:[~2014-11-06 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 17:21 Vitaly Kuznetsov [this message]
2014-11-06 17:21 ` [PATCH 1/2] Drivers: hv: vss: Introduce timeout for communication with userspace Vitaly Kuznetsov
2014-11-06 17:21 ` [PATCH 2/2] Drivers: hv: kvp,vss: Fast propagation of userspace communication failure Vitaly Kuznetsov

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=1415294485-23945-1-git-send-email-vkuznets@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®