search for: interurpt

...t;I'm not sure the regression is due to interrupts. > >>It would make sense for CPU but why would it > >>hurt transaction rate? > > > >Anyway guest need to take some cycles to handle tx interrupts. > >And transaction rate does increase if we coalesces more tx interurpts. > >> > >> > >>It's possible that we are deferring kicks too much due to BQL. > >> > >>As an experiment: do we get any of it back if we do > >>- if (kick || netif_xmit_stopped(txq)) > >>- virtqueue_kick(sq-&gt...

...t;I'm not sure the regression is due to interrupts. > >>It would make sense for CPU but why would it > >>hurt transaction rate? > > > >Anyway guest need to take some cycles to handle tx interrupts. > >And transaction rate does increase if we coalesces more tx interurpts. > >> > >> > >>It's possible that we are deferring kicks too much due to BQL. > >> > >>As an experiment: do we get any of it back if we do > >>- if (kick || netif_xmit_stopped(txq)) > >>- virtqueue_kick(sq-&gt...

...nterrupts. > >> >>It would make sense for CPU but why would it > >> >>hurt transaction rate? > >> > > >> >Anyway guest need to take some cycles to handle tx interrupts. > >> >And transaction rate does increase if we coalesces more tx interurpts. > >> >> > >> >> > >> >>It's possible that we are deferring kicks too much due to BQL. > >> >> > >> >>As an experiment: do we get any of it back if we do > >> >>- if (kick || netif_xmit_stopped(txq...

...nterrupts. > >> >>It would make sense for CPU but why would it > >> >>hurt transaction rate? > >> > > >> >Anyway guest need to take some cycles to handle tx interrupts. > >> >And transaction rate does increase if we coalesces more tx interurpts. > >> >> > >> >> > >> >>It's possible that we are deferring kicks too much due to BQL. > >> >> > >> >>As an experiment: do we get any of it back if we do > >> >>- if (kick || netif_xmit_stopped(txq...

...> >>It would make sense for CPU but why would it > > >> >>hurt transaction rate? > > >> > > > >> >Anyway guest need to take some cycles to handle tx interrupts. > > >> >And transaction rate does increase if we coalesces more tx interurpts. > > >> >> > > >> >> > > >> >>It's possible that we are deferring kicks too much due to BQL. > > >> >> > > >> >>As an experiment: do we get any of it back if we do > > >> >>- if (...

....rate. (reduce 40%-80% tx intrs) > > I'm not sure the regression is due to interrupts. > It would make sense for CPU but why would it > hurt transaction rate? Anyway guest need to take some cycles to handle tx interrupts. And transaction rate does increase if we coalesces more tx interurpts. > > > It's possible that we are deferring kicks too much due to BQL. > > As an experiment: do we get any of it back if we do > - if (kick || netif_xmit_stopped(txq)) > - virtqueue_kick(sq->vq); > + virtqueue_kick(sq->vq); > ?...

....rate. (reduce 40%-80% tx intrs) > > I'm not sure the regression is due to interrupts. > It would make sense for CPU but why would it > hurt transaction rate? Anyway guest need to take some cycles to handle tx interrupts. And transaction rate does increase if we coalesces more tx interurpts. > > > It's possible that we are deferring kicks too much due to BQL. > > As an experiment: do we get any of it back if we do > - if (kick || netif_xmit_stopped(txq)) > - virtqueue_kick(sq->vq); > + virtqueue_kick(sq->vq); > ?...

...s due to interrupts. >> >>It would make sense for CPU but why would it >> >>hurt transaction rate? >> > >> >Anyway guest need to take some cycles to handle tx interrupts. >> >And transaction rate does increase if we coalesces more tx >> interurpts. >> >> >> >> >> >>It's possible that we are deferring kicks too much due to BQL. >> >> >> >>As an experiment: do we get any of it back if we do >> >>- if (kick || netif_xmit_stopped(txq)) >> >>-...

...s due to interrupts. >> >>It would make sense for CPU but why would it >> >>hurt transaction rate? >> > >> >Anyway guest need to take some cycles to handle tx interrupts. >> >And transaction rate does increase if we coalesces more tx >> interurpts. >> >> >> >> >> >>It's possible that we are deferring kicks too much due to BQL. >> >> >> >>As an experiment: do we get any of it back if we do >> >>- if (kick || netif_xmit_stopped(txq)) >> >>-...

...d make sense for CPU but why would it > > > >> >>hurt transaction rate? > > > >> > > > > >> >Anyway guest need to take some cycles to handle tx interrupts. > > > >> >And transaction rate does increase if we coalesces more tx interurpts. > > > >> >> > > > >> >> > > > >> >>It's possible that we are deferring kicks too much due to BQL. > > > >> >> > > > >> >>As an experiment: do we get any of it back if we do > > >...

...;> >> I'm not sure the regression is due to interrupts. >> It would make sense for CPU but why would it >> hurt transaction rate? > > Anyway guest need to take some cycles to handle tx interrupts. > And transaction rate does increase if we coalesces more tx > interurpts. >> >> >> It's possible that we are deferring kicks too much due to BQL. >> >> As an experiment: do we get any of it back if we do >> - if (kick || netif_xmit_stopped(txq)) >> - virtqueue_kick(sq->vq); >> + vir...

...;> >> I'm not sure the regression is due to interrupts. >> It would make sense for CPU but why would it >> hurt transaction rate? > > Anyway guest need to take some cycles to handle tx interrupts. > And transaction rate does increase if we coalesces more tx > interurpts. >> >> >> It's possible that we are deferring kicks too much due to BQL. >> >> As an experiment: do we get any of it back if we do >> - if (kick || netif_xmit_stopped(txq)) >> - virtqueue_kick(sq->vq); >> + vir...

Hello: We used to orphan packets before transmission for virtio-net. This breaks socket accounting and can lead serveral functions won't work, e.g: - Byte Queue Limit depends on tx completion nofication to work. - Packet Generator depends on tx completion nofication for the last transmitted packet to complete. - TCP Small Queue depends on proper accounting of sk_wmem_alloc to work. This

Hello: We used to orphan packets before transmission for virtio-net. This breaks socket accounting and can lead serveral functions won't work, e.g: - Byte Queue Limit depends on tx completion nofication to work. - Packet Generator depends on tx completion nofication for the last transmitted packet to complete. - TCP Small Queue depends on proper accounting of sk_wmem_alloc to work. This