Displaying 4 results from an estimated 4 matches for "allow_zero_num_buff".
2017 Mar 01
1
[virtio-dev] packed ring layout proposal v2
...struct sk_buff *curr_skb = head_skb;
373
374 if (unlikely(!curr_skb))
375 goto err_skb;
==> 376 while (--num_buf) {
That means, if we want to do that, it needs an extra feature flag
(either a global feature flag or a desc flag), something like
ALLOW_ZERO_NUM_BUFFERS. Or even, make it allowable in virtio 1.1
(virtio 0.95/1.0 won't benifit from it though).
Does it make sense to you?
> Make each buffer
> MTU sized and it'll fit without merging. Linux used not to, it only
> started doing this to save memory aggressively. I don't think
&g...
2017 Mar 01
2
[virtio-dev] packed ring layout proposal v2
On Tue, Feb 28, 2017 at 01:02:18PM +0800, Yuanhan Liu wrote:
> On Wed, Feb 08, 2017 at 05:20:14AM +0200, Michael S. Tsirkin wrote:
> > This is an update from v1 version.
> > Changes:
> > - update event suppression mechanism
> > - separate options for indirect and direct s/g
> > - lots of new features
> >
> > ---
> >
> > Performance
2017 Mar 01
2
[virtio-dev] packed ring layout proposal v2
On Tue, Feb 28, 2017 at 01:02:18PM +0800, Yuanhan Liu wrote:
> On Wed, Feb 08, 2017 at 05:20:14AM +0200, Michael S. Tsirkin wrote:
> > This is an update from v1 version.
> > Changes:
> > - update event suppression mechanism
> > - separate options for indirect and direct s/g
> > - lots of new features
> >
> > ---
> >
> > Performance
2017 Mar 01
0
[virtio-dev] packed ring layout proposal v2
...skb;
> 373
> 374 if (unlikely(!curr_skb))
> 375 goto err_skb;
> ==> 376 while (--num_buf) {
>
> That means, if we want to do that, it needs an extra feature flag
> (either a global feature flag or a desc flag), something like
> ALLOW_ZERO_NUM_BUFFERS. Or even, make it allowable in virtio 1.1
> (virtio 0.95/1.0 won't benifit from it though).
>
> Does it make sense to you?
Right and then we could use a descriptor flag "header is all 0s".
For virtio 1.0 we could put these in the used ring instead.
>
> > Make...