Displaying 8 results from an estimated 8 matches for "hv_kvp_msg".
Did you mean:
hv_ku_msg
2010 Dec 08
0
No subject
...timeout.
+ */
+ if (cancel_delayed_work_sync(&kvp_work))
+ kvp_respond_to_host(message->kvp_key,
+ message->kvp_value,
+ !strlen(message->kvp_key));=
+ }
+}
+
+static int
+kvp_send_key(int index)
+{
+ struct cn_msg *msg;
+
+ msg =3D kzalloc(sizeof(*msg) + sizeof(struct hv_kvp_msg) , =
GFP_ATOMIC);
+
+ if (msg) {
+ msg->id.idx =3D CN_KVP_IDX;
+ msg->id.val =3D CN_KVP_VAL;
+ msg->seq =3D KVP_KERNEL_GET;
+ ((struct hv_ku_msg *)msg->data)->kvp_index =3D index;
+ msg->len =3D sizeof(struct hv_ku_msg);
+ cn_netlink_send(msg, 0, GFP_ATOMIC);
+ kfree(msg);...
2010 Dec 08
0
No subject
...timeout.
+ */
+ if (cancel_delayed_work_sync(&kvp_work))
+ kvp_respond_to_host(message->kvp_key,
+ message->kvp_value,
+ !strlen(message->kvp_key));=
+ }
+}
+
+static int
+kvp_send_key(int index)
+{
+ struct cn_msg *msg;
+
+ msg =3D kzalloc(sizeof(*msg) + sizeof(struct hv_kvp_msg) , =
GFP_ATOMIC);
+
+ if (msg) {
+ msg->id.idx =3D CN_KVP_IDX;
+ msg->id.val =3D CN_KVP_VAL;
+ msg->seq =3D KVP_KERNEL_GET;
+ ((struct hv_ku_msg *)msg->data)->kvp_index =3D index;
+ msg->len =3D sizeof(struct hv_ku_msg);
+ cn_netlink_send(msg, 0, GFP_ATOMIC);
+ kfree(msg);...
2010 Dec 17
0
[PATCH 3/4] Staging: hv: Implement key/value pair (KVP)
...the timeout.
+ */
+ if (cancel_delayed_work_sync(&kvp_work))
+ kvp_respond_to_host(message->kvp_key,
+ message->kvp_value,
+ !strlen(message->kvp_key));
+ }
+}
+
+static int
+kvp_send_key(int index)
+{
+ struct cn_msg *msg;
+
+ msg = kzalloc(sizeof(*msg) + sizeof(struct hv_kvp_msg) , GFP_ATOMIC);
+
+ if (msg) {
+ msg->id.idx = CN_KVP_IDX;
+ msg->id.val = CN_KVP_VAL;
+ msg->seq = KVP_KERNEL_GET;
+ ((struct hv_ku_msg *)msg->data)->kvp_index = index;
+ msg->len = sizeof(struct hv_ku_msg);
+ cn_netlink_send(msg, 0, GFP_ATOMIC);
+ kfree(msg);
+ return 0...
2010 Dec 17
0
[PATCH 3/4] Staging: hv: Implement key/value pair (KVP)
...the timeout.
+ */
+ if (cancel_delayed_work_sync(&kvp_work))
+ kvp_respond_to_host(message->kvp_key,
+ message->kvp_value,
+ !strlen(message->kvp_key));
+ }
+}
+
+static int
+kvp_send_key(int index)
+{
+ struct cn_msg *msg;
+
+ msg = kzalloc(sizeof(*msg) + sizeof(struct hv_kvp_msg) , GFP_ATOMIC);
+
+ if (msg) {
+ msg->id.idx = CN_KVP_IDX;
+ msg->id.val = CN_KVP_VAL;
+ msg->seq = KVP_KERNEL_GET;
+ ((struct hv_ku_msg *)msg->data)->kvp_index = index;
+ msg->len = sizeof(struct hv_ku_msg);
+ cn_netlink_send(msg, 0, GFP_ATOMIC);
+ kfree(msg);
+ return 0...
2010 Nov 22
1
[PATCH 3/3]: An implementation of HyperV KVP functionality
An implementation of key/value pair feature (KVP) for Linux on HyperV. In this version of the patch I have addressed all the comments I have received to date. I have also included the code for the user-level daemon here for your reference.
Signed-off-by: K. Y. Srinivasan <ksrinivasan at novell.com>
-------------- next part --------------
An embedded and charset-unspecified text was
2010 Nov 22
1
[PATCH 3/3]: An implementation of HyperV KVP functionality
An implementation of key/value pair feature (KVP) for Linux on HyperV. In this version of the patch I have addressed all the comments I have received to date. I have also included the code for the user-level daemon here for your reference.
Signed-off-by: K. Y. Srinivasan <ksrinivasan at novell.com>
-------------- next part --------------
An embedded and charset-unspecified text was
2011 Sep 08
25
[PATCH 0000/0025] Staging: hv: Driver cleanup
Address Greg's VmBus audit comments:
1) Leverage driver_data field in struct hv_vmbus_device_id to
simplify driver code.
2) Make the util driver conform to the Linux Driver Model.
3) Get rid of the ext field in struct hv_device by using the
driver specific data functionality.
4) Other general cleanup.
Regards,
K. Y
2011 Sep 08
25
[PATCH 0000/0025] Staging: hv: Driver cleanup
Address Greg's VmBus audit comments:
1) Leverage driver_data field in struct hv_vmbus_device_id to
simplify driver code.
2) Make the util driver conform to the Linux Driver Model.
3) Get rid of the ext field in struct hv_device by using the
driver specific data functionality.
4) Other general cleanup.
Regards,
K. Y