Displaying 20 results from an estimated 20000 matches similar to: "[PATCHv4 0/2] vhost: a kernel-level virtio server"
2009 Aug 27
0
[PATCHv5 0/3] vhost: a kernel-level virtio server
Rusty, ok, I think I've addressed your comments so far here.
Coming next:
- TSO
- tap support
Thanks!
---
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce virtualization
overhead for virtio by removing system calls on data path,
without guest changes. For virtio-net, this removes up to
4 system calls per packet: vm exit for kick,
2009 Aug 27
0
[PATCHv5 0/3] vhost: a kernel-level virtio server
Rusty, ok, I think I've addressed your comments so far here.
Coming next:
- TSO
- tap support
Thanks!
---
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce virtualization
overhead for virtio by removing system calls on data path,
without guest changes. For virtio-net, this removes up to
4 system calls per packet: vm exit for kick,
2009 Aug 13
0
[PATCHv3 0/2] vhost: a kernel-level virtio server
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce virtualization
overhead for virtio by removing system calls on data path,
without guest changes. For virtio-net, this removes up to
4 system calls per packet: vm exit for kick, reentry for kick,
iothread wakeup for packet, interrupt injection for packet.
Some more detailed description attached
2009 Aug 13
0
[PATCHv3 0/2] vhost: a kernel-level virtio server
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce virtualization
overhead for virtio by removing system calls on data path,
without guest changes. For virtio-net, this removes up to
4 system calls per packet: vm exit for kick, reentry for kick,
iothread wakeup for packet, interrupt injection for packet.
Some more detailed description attached
2009 Aug 11
1
[PATCHv2 0/2] vhost: a kernel-level virtio server
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce virtualization
overhead for virtio by removing system calls on data path,
without guest changes. For virtio-net, this removes up to
4 system calls per packet: vm exit for kick, reentry for kick,
iothread wakeup for packet, interrupt injection for packet.
Some more detailed description attached
2009 Aug 11
1
[PATCHv2 0/2] vhost: a kernel-level virtio server
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce virtualization
overhead for virtio by removing system calls on data path,
without guest changes. For virtio-net, this removes up to
4 system calls per packet: vm exit for kick, reentry for kick,
iothread wakeup for packet, interrupt injection for packet.
Some more detailed description attached
2009 Nov 02
0
[PATCHv6 0/3] vhost: a kernel-level virtio server
Rusty, ok, I think I've addressed your comments so far here. In
particular I have added write logging for live migration, indirect
buffers and virtio net header (enables gso). I'd like this to go
into linux-next, through your tree, and hopefully 2.6.33.
What do you think?
---
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce
2009 Nov 02
0
[PATCHv6 0/3] vhost: a kernel-level virtio server
Rusty, ok, I think I've addressed your comments so far here. In
particular I have added write logging for live migration, indirect
buffers and virtio net header (enables gso). I'd like this to go
into linux-next, through your tree, and hopefully 2.6.33.
What do you think?
---
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce
2009 Nov 03
0
[PATCHv7 0/3] vhost: a kernel-level virtio server
Rusty, ok, I think I've addressed all comments so far here. In
particular I have added write logging for live migration, indirect
buffers and virtio net header (enables gso). I'd like this to go
into linux-next, through your tree, and hopefully 2.6.33.
What do you think?
---
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce
2009 Nov 03
0
[PATCHv7 0/3] vhost: a kernel-level virtio server
Rusty, ok, I think I've addressed all comments so far here. In
particular I have added write logging for live migration, indirect
buffers and virtio net header (enables gso). I'd like this to go
into linux-next, through your tree, and hopefully 2.6.33.
What do you think?
---
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce
2009 Nov 09
0
[PATCHv9 0/3] vhost: a kernel-level virtio server
Ok, I think I've addressed all comments so far here, and it still seems
to work :). Please take a look. I basically ended up accepting all
Rusty's suggestions, except I did not get rid of avail_idx field in vq:
I don't (yet?) understand what's wrong with it, if any, and it seems
required for correct implementation of notify on empty. I tried
adding comment where it's changed
2009 Nov 09
0
[PATCHv9 0/3] vhost: a kernel-level virtio server
Ok, I think I've addressed all comments so far here, and it still seems
to work :). Please take a look. I basically ended up accepting all
Rusty's suggestions, except I did not get rid of avail_idx field in vq:
I don't (yet?) understand what's wrong with it, if any, and it seems
required for correct implementation of notify on empty. I tried
adding comment where it's changed
2009 Nov 04
1
[PATCHv8 0/3] vhost: a kernel-level virtio server
Ok, I think I've addressed all comments so far here.
Rusty, I'd like this to go into linux-next, through your tree, and
hopefully 2.6.33. What do you think?
---
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce virtualization
overhead for virtio by removing system calls on data path,
without guest changes. For virtio-net, this
2009 Nov 04
1
[PATCHv8 0/3] vhost: a kernel-level virtio server
Ok, I think I've addressed all comments so far here.
Rusty, I'd like this to go into linux-next, through your tree, and
hopefully 2.6.33. What do you think?
---
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce virtualization
overhead for virtio by removing system calls on data path,
without guest changes. For virtio-net, this
2009 Aug 19
0
[PATCHv4 1/2] mm: export use_mm/unuse_mm to modules
vhost net module wants to do copy to/from user from a kernel thread,
which needs use_mm (like what fs/aio has). Move that into mm/ and
export to modules.
Acked-by: Andrew Morton <akpm at linux-foundation.org>
Acked-by: Andrea Arcangeli <aarcange at redhat.com>
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
fs/aio.c | 47
2009 Aug 19
0
[PATCHv4 1/2] mm: export use_mm/unuse_mm to modules
vhost net module wants to do copy to/from user from a kernel thread,
which needs use_mm (like what fs/aio has). Move that into mm/ and
export to modules.
Acked-by: Andrew Morton <akpm at linux-foundation.org>
Acked-by: Andrea Arcangeli <aarcange at redhat.com>
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
fs/aio.c | 47
2020 Apr 04
0
[PATCH 4/6] kernel: move use_mm/unuse_mm to kthread.c
These helpers are only for use with kernel threads, and I will tie them
more into the kthread infrastructure going forward. Also move the
prototypes to kthread.h - mmu_context.h was a little weird to start with
as it otherwise contains very low-level MM bits.
Signed-off-by: Christoph Hellwig <hch at lst.de>
---
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h | 1 +
2009 Aug 11
1
[PATCHv2 1/2] mm: export use_mm/unuse_mm to modules
vhost net module wants to do copy to/from user from a kernel thread,
which needs use_mm (like what fs/aio has). Move that into mm/ and
export to modules.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
fs/aio.c | 47 +----------------------------------
include/linux/mmu_context.h | 9 ++++++
mm/Makefile | 2 +-
mm/mmu_context.c
2009 Aug 11
1
[PATCHv2 1/2] mm: export use_mm/unuse_mm to modules
vhost net module wants to do copy to/from user from a kernel thread,
which needs use_mm (like what fs/aio has). Move that into mm/ and
export to modules.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
fs/aio.c | 47 +----------------------------------
include/linux/mmu_context.h | 9 ++++++
mm/Makefile | 2 +-
mm/mmu_context.c
2009 Aug 27
1
[PATCHv5 1/3] mm: export use_mm/unuse_mm to modules
vhost net module wants to do copy to/from user from a kernel thread,
which needs use_mm (like what fs/aio has). Move that into mm/ and
export to modules.
Acked-by: Andrew Morton <akpm at linux-foundation.org>
Acked-by: Andrea Arcangeli <aarcange at redhat.com>
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
fs/aio.c | 47