similar to: [PATCH v4 26/42] vhost/net: force len for TX to host endian

Displaying 20 results from an estimated 3000 matches similar to: "[PATCH v4 26/42] vhost/net: force len for TX to host endian"

2014 Nov 26
2
[PATCH v4 26/42] vhost/net: force len for TX to host endian
On Wed, Nov 26, 2014 at 03:31:02PM +0100, Cornelia Huck wrote: > On Tue, 25 Nov 2014 18:43:14 +0200 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > We use native endian-ness internally but never > > expose it to guest. > > > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> > > --- > > drivers/vhost/net.c | 10
2014 Nov 26
2
[PATCH v4 26/42] vhost/net: force len for TX to host endian
On Wed, Nov 26, 2014 at 03:31:02PM +0100, Cornelia Huck wrote: > On Tue, 25 Nov 2014 18:43:14 +0200 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > We use native endian-ness internally but never > > expose it to guest. > > > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> > > --- > > drivers/vhost/net.c | 10
2014 Nov 30
2
[PATCH v7 30/46] vhost/net: force len for TX to host endian
vhost/net keeps a copy of some used ring but (ab)uses length field for internal house-keeping. This works because for tx used length is always 0. Suppress sparse errors: we use native endian-ness internally but never expose it to guest. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> Reviewed-by: Jason Wang <jasowang at redhat.com> --- drivers/vhost/net.c | 10 +++++----- 1
2014 Nov 30
2
[PATCH v7 30/46] vhost/net: force len for TX to host endian
vhost/net keeps a copy of some used ring but (ab)uses length field for internal house-keeping. This works because for tx used length is always 0. Suppress sparse errors: we use native endian-ness internally but never expose it to guest. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> Reviewed-by: Jason Wang <jasowang at redhat.com> --- drivers/vhost/net.c | 10 +++++----- 1
2014 Nov 27
1
[PATCH v6 30/46] vhost/net: force len for TX to host endian
vhost/net keeps a copy of some used ring but (ab)uses length field for internal house-keeping. This works because for tx used length is always 0. Suppress sparse errors: we use native endian-ness internally but never expose it to guest. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/vhost/net.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git
2014 Nov 27
1
[PATCH v6 30/46] vhost/net: force len for TX to host endian
vhost/net keeps a copy of some used ring but (ab)uses length field for internal house-keeping. This works because for tx used length is always 0. Suppress sparse errors: we use native endian-ness internally but never expose it to guest. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/vhost/net.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git
2014 Nov 26
0
[PATCH v4 26/42] vhost/net: force len for TX to host endian
On Tue, 25 Nov 2014 18:43:14 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > We use native endian-ness internally but never > expose it to guest. > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> > --- > drivers/vhost/net.c | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff --git a/drivers/vhost/net.c
2014 Nov 26
0
[PATCH v4 26/42] vhost/net: force len for TX to host endian
On Wed, 26 Nov 2014 16:44:00 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > On Wed, Nov 26, 2014 at 03:31:02PM +0100, Cornelia Huck wrote: > > On Tue, 25 Nov 2014 18:43:14 +0200 > > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > > > We use native endian-ness internally but never > > > expose it to guest. >
2020 Jun 03
1
[PATCH RFC 08/13] vhost/net: convert to new API: heads->bufs
On 2020/6/2 ??9:06, Michael S. Tsirkin wrote: > Convert vhost net to use the new format-agnostic API. > In particular, don't poke at vq internals such as the > heads array. > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> > --- > drivers/vhost/net.c | 153 +++++++++++++++++++++++--------------------- > 1 file changed, 81 insertions(+), 72 deletions(-)
2014 Nov 24
0
[PATCH v3 25/41] vhost/net: force len for TX to host endian
We use native endian-ness internally but never expose it to guest. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/vhost/net.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c index 8dae2f7..dce5c58 100644 --- a/drivers/vhost/net.c +++ b/drivers/vhost/net.c @@ -48,15 +48,15 @@
2014 Nov 27
0
[PATCH v5 29/45] vhost/net: force len for TX to host endian
vhost/net keeps a copy of some used ring but (ab)uses length field for internal house-keeping. This works because for tx used length is always 0. Suppress sparse errors: we use native endian-ness internally but never expose it to guest. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/vhost/net.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git
2014 Dec 01
0
[PATCH v7 30/46] vhost/net: force len for TX to host endian
On Sun, 30 Nov 2014 17:11:44 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > vhost/net keeps a copy of some used ring but (ab)uses length > field for internal house-keeping. This works because > for tx used length is always 0. > Suppress sparse errors: we use native endian-ness internally but never > expose it to guest. I admit that I find this patch
2014 Dec 01
0
[PATCH v8 31/50] vhost/net: force len for TX to host endian
vhost/net keeps a copy of the used ring in host memory but (ab)uses the length field for internal house-keeping. This works because the length in the used ring for tx is always 0. In order to suppress sparse warnings, we force native endianness here. Note that these values are never exposed to guests. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> Reviewed-by: Jason Wang <jasowang
2014 Nov 24
0
[PATCH v3 25/41] vhost/net: force len for TX to host endian
We use native endian-ness internally but never expose it to guest. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/vhost/net.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c index 8dae2f7..dce5c58 100644 --- a/drivers/vhost/net.c +++ b/drivers/vhost/net.c @@ -48,15 +48,15 @@
2014 Nov 27
0
[PATCH v5 29/45] vhost/net: force len for TX to host endian
vhost/net keeps a copy of some used ring but (ab)uses length field for internal house-keeping. This works because for tx used length is always 0. Suppress sparse errors: we use native endian-ness internally but never expose it to guest. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/vhost/net.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git
2014 Dec 01
0
[PATCH v7 30/46] vhost/net: force len for TX to host endian
On Sun, 30 Nov 2014 17:11:44 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > vhost/net keeps a copy of some used ring but (ab)uses length > field for internal house-keeping. This works because > for tx used length is always 0. > Suppress sparse errors: we use native endian-ness internally but never > expose it to guest. I admit that I find this patch
2014 Dec 01
0
[PATCH v8 31/50] vhost/net: force len for TX to host endian
vhost/net keeps a copy of the used ring in host memory but (ab)uses the length field for internal house-keeping. This works because the length in the used ring for tx is always 0. In order to suppress sparse warnings, we force native endianness here. Note that these values are never exposed to guests. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> Reviewed-by: Jason Wang <jasowang
2012 Nov 01
9
[PATCHv3 net-next 0/8] enable/disable zero copy tx dynamically
tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b, however you can only enable this mode if you know your workload does not trigger heavy guest to host/host to guest traffic - otherwise you get a (minor) performance regression. This patchset addresses this problem by notifying the owner device when callback is invoked because of a data copy. This makes it possible to
2012 Nov 01
9
[PATCHv3 net-next 0/8] enable/disable zero copy tx dynamically
tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b, however you can only enable this mode if you know your workload does not trigger heavy guest to host/host to guest traffic - otherwise you get a (minor) performance regression. This patchset addresses this problem by notifying the owner device when callback is invoked because of a data copy. This makes it possible to
2012 Oct 31
8
[PATCHv2 net-next 0/8] enable/disable zero copy tx dynamically
tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b, however you can only enable this mode if you know your workload does not trigger heavy guest to host/host to guest traffic - otherwise you get a (minor) performance regression. This patchset addresses this problem by notifying the owner device when callback is invoked because of a data copy. This makes it possible to