search for: impliestw

Displaying 8 results from an estimated 8 matches for "impliestw".

Did you mean: implies
2017 Sep 01
2
[PATCH net-next] virtio-net: invoke zerocopy callback on xmit path if no tx napi
>>> This is not a 50/50 split, which impliesTw that some packets from the >>> large >>> packet flow are still converted to copying. Without the change the rate >>> without queue was 80k zerocopy vs 80k copy, so this choice of >>> (vq->num >> 2) appears too conservative. >>> >>> Howe...
2017 Sep 01
2
[PATCH net-next] virtio-net: invoke zerocopy callback on xmit path if no tx napi
>>> This is not a 50/50 split, which impliesTw that some packets from the >>> large >>> packet flow are still converted to copying. Without the change the rate >>> without queue was 80k zerocopy vs 80k copy, so this choice of >>> (vq->num >> 2) appears too conservative. >>> >>> Howe...
2017 Sep 01
2
[PATCH net-next] virtio-net: invoke zerocopy callback on xmit path if no tx napi
...68535 > > Both flows continue to send at more or less normal rate, with only > sender B observing massive drops at the netem. > > With the queue removed the rate reverts to > > zerocopy=58878 copy=110239 > zerocopy=58833 copy=110207 > > This is not a 50/50 split, which impliesTw that some packets from the large > packet flow are still converted to copying. Without the change the rate > without queue was 80k zerocopy vs 80k copy, so this choice of > (vq->num >> 2) appears too conservative. > > However, testing with (vq->num >> 1) was not as...
2017 Sep 01
2
[PATCH net-next] virtio-net: invoke zerocopy callback on xmit path if no tx napi
...68535 > > Both flows continue to send at more or less normal rate, with only > sender B observing massive drops at the netem. > > With the queue removed the rate reverts to > > zerocopy=58878 copy=110239 > zerocopy=58833 copy=110207 > > This is not a 50/50 split, which impliesTw that some packets from the large > packet flow are still converted to copying. Without the change the rate > without queue was 80k zerocopy vs 80k copy, so this choice of > (vq->num >> 2) appears too conservative. > > However, testing with (vq->num >> 1) was not as...
2017 Sep 05
1
[PATCH net-next] virtio-net: invoke zerocopy callback on xmit path if no tx napi
On Mon, Sep 4, 2017 at 5:03 AM, Jason Wang <jasowang at redhat.com> wrote: > > > On 2017?09?02? 00:17, Willem de Bruijn wrote: >>>>> >>>>> This is not a 50/50 split, which impliesTw that some packets from the >>>>> large >>>>> packet flow are still converted to copying. Without the change the rate >>>>> without queue was 80k zerocopy vs 80k copy, so this choice of >>>>> (vq->num >> 2) appears too conservative...
2017 Sep 05
1
[PATCH net-next] virtio-net: invoke zerocopy callback on xmit path if no tx napi
On Mon, Sep 4, 2017 at 5:03 AM, Jason Wang <jasowang at redhat.com> wrote: > > > On 2017?09?02? 00:17, Willem de Bruijn wrote: >>>>> >>>>> This is not a 50/50 split, which impliesTw that some packets from the >>>>> large >>>>> packet flow are still converted to copying. Without the change the rate >>>>> without queue was 80k zerocopy vs 80k copy, so this choice of >>>>> (vq->num >> 2) appears too conservative...
2017 Sep 04
0
[PATCH net-next] virtio-net: invoke zerocopy callback on xmit path if no tx napi
On 2017?09?02? 00:17, Willem de Bruijn wrote: >>>> This is not a 50/50 split, which impliesTw that some packets from the >>>> large >>>> packet flow are still converted to copying. Without the change the rate >>>> without queue was 80k zerocopy vs 80k copy, so this choice of >>>> (vq->num >> 2) appears too conservative. >>>&g...
2017 Sep 01
0
[PATCH net-next] virtio-net: invoke zerocopy callback on xmit path if no tx napi
...nue to send at more or less normal rate, with only >> sender B observing massive drops at the netem. >> >> With the queue removed the rate reverts to >> >> zerocopy=58878 copy=110239 >> zerocopy=58833 copy=110207 >> >> This is not a 50/50 split, which impliesTw that some packets from the >> large >> packet flow are still converted to copying. Without the change the rate >> without queue was 80k zerocopy vs 80k copy, so this choice of >> (vq->num >> 2) appears too conservative. >> >> However, testing with (vq-&g...