This series converts kvp/vss daemons to use misc char devices instead of
netlink for userspace/kernel communication and then updates fcopy to be
consistent with kvp/vss.
Userspace/kernel communication via netlink has a number of issues:
- It is hard for userspace to figure out if the kernel part was loaded or not
and this fact can change as there is a way to enable/disable the service from
host side. Racy daemon startup is also a problem.
- When the userspace daemon restarts/dies kernel part doesn't receive a
notification.
- Netlink communication is not stable under heavy load.
- ...
RFC: I'm a bit puzzled on how to split commits 1 and 2 avoiding breakages.
Commit 3 can definitely be split, however, it is consistent with commits 1 and
2 at this moment and I'm not sure such split will simplify the review.
Vitaly Kuznetsov (3):
Drivers: hv: kvp: convert userspace/kernel communication to using char
device
Drivers: hv: vss: convert userspace/kernel communication to using char
device
Drivers: hv: fcopy: make it consistent with vss/kvp
drivers/hv/hv_fcopy.c | 395 +++++++++++++++++++++++++------------------
drivers/hv/hv_kvp.c | 396 +++++++++++++++++++++++++++-----------------
drivers/hv/hv_snapshot.c | 335 +++++++++++++++++++++++++++----------
include/uapi/linux/hyperv.h | 10 ++
tools/hv/hv_fcopy_daemon.c | 48 ++++--
tools/hv/hv_kvp_daemon.c | 187 ++++-----------------
tools/hv/hv_vss_daemon.c | 141 +++-------------
7 files changed, 824 insertions(+), 688 deletions(-)
--
1.9.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
