search for: credit2mem

Displaying 6 results from an estimated 6 matches for "credit2mem".

2019 Oct 11
4
[PATCH v4 1/5] vsock/virtio: limit the memory used per-socket
...ations and looking better to our credit mechanism: buf_alloc = 256 KB (default, tunable through setsockopt) sizeof(struct virtio_vsock_pkt) = 128 - guest (we use preallocated 4 KB buffers to receive packets, copying small packet - < 128 -) worst_case = 129 buf_size = 4 KB credit2mem = (buf_size + sizeof(struct virtio_vsock_pkt)) / worst_case = 32 credit_published = buf_alloc / credit2mem = ~8 KB Space for just 2 full packet (4 KB) - host (we copy packets from the vring, allocating the space for the payload) worst_case = 1 buf_size = 1 credit2mem = (buf_...
2019 Oct 11
4
[PATCH v4 1/5] vsock/virtio: limit the memory used per-socket
...ations and looking better to our credit mechanism: buf_alloc = 256 KB (default, tunable through setsockopt) sizeof(struct virtio_vsock_pkt) = 128 - guest (we use preallocated 4 KB buffers to receive packets, copying small packet - < 128 -) worst_case = 129 buf_size = 4 KB credit2mem = (buf_size + sizeof(struct virtio_vsock_pkt)) / worst_case = 32 credit_published = buf_alloc / credit2mem = ~8 KB Space for just 2 full packet (4 KB) - host (we copy packets from the vring, allocating the space for the payload) worst_case = 1 buf_size = 1 credit2mem = (buf_...
2019 Oct 11
0
[PATCH v4 1/5] vsock/virtio: limit the memory used per-socket
...nism: > > buf_alloc = 256 KB (default, tunable through setsockopt) > sizeof(struct virtio_vsock_pkt) = 128 > > - guest (we use preallocated 4 KB buffers to receive packets, copying > small packet - < 128 -) > worst_case = 129 > buf_size = 4 KB > credit2mem = (buf_size + sizeof(struct virtio_vsock_pkt)) / worst_case = 32 Making virtio_vsock_pkt smaller will help btw. E.g. why keep a work struct per packet? do we need the header there? etc etc. > > credit_published = buf_alloc / credit2mem = ~8 KB > Space for just 2 full packet (4 K...
2019 Oct 14
0
[PATCH v4 1/5] vsock/virtio: limit the memory used per-socket
...nism: > > buf_alloc = 256 KB (default, tunable through setsockopt) > sizeof(struct virtio_vsock_pkt) = 128 > > - guest (we use preallocated 4 KB buffers to receive packets, copying > small packet - < 128 -) > worst_case = 129 > buf_size = 4 KB > credit2mem = (buf_size + sizeof(struct virtio_vsock_pkt)) / worst_case = 32 > > credit_published = buf_alloc / credit2mem = ~8 KB > Space for just 2 full packet (4 KB) > > - host (we copy packets from the vring, allocating the space for the payload) > worst_case = 1 >...
2019 Jul 17
22
[PATCH v4 0/5] vsock/virtio: optimizations to increase the throughput
This series tries to increase the throughput of virtio-vsock with slight changes. While I was testing the v2 of this series I discovered an huge use of memory, so I added patch 1 to mitigate this issue. I put it in this series in order to better track the performance trends. v4: - rebased all patches on current master (conflicts is Patch 4) - Patch 1: added Stefan's R-b - Patch 3: removed
2019 Jul 17
22
[PATCH v4 0/5] vsock/virtio: optimizations to increase the throughput
This series tries to increase the throughput of virtio-vsock with slight changes. While I was testing the v2 of this series I discovered an huge use of memory, so I added patch 1 to mitigate this issue. I put it in this series in order to better track the performance trends. v4: - rebased all patches on current master (conflicts is Patch 4) - Patch 1: added Stefan's R-b - Patch 3: removed