Displaying 4 results from an estimated 4 matches for "seg_num".
2017 Mar 01
1
[virtio-dev] packed ring layout proposal v2
...d.
So while writing this email, I was thinking maybe we could not set
num_buffers to 1 when there is only one desc (let it be 0 and let
num_buffers == 0 imply num_buffers = 1). I'm not quite sure we can
do that now, thus I checked the DPDK code and found it's Okay.
896 seg_num = header->num_buffers;
897
898 if (seg_num == 0)
899 seg_num = 1;
I then also checked linux kernel code, and found it's not okay as
the code depends on the value being set correctly:
==> 365 u16 num_buf = virtio16_to_cpu(vi-&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
...email, I was thinking maybe we could not set
> num_buffers to 1 when there is only one desc (let it be 0 and let
> num_buffers == 0 imply num_buffers = 1). I'm not quite sure we can
> do that now, thus I checked the DPDK code and found it's Okay.
>
> 896 seg_num = header->num_buffers;
> 897
> 898 if (seg_num == 0)
> 899 seg_num = 1;
>
>
> I then also checked linux kernel code, and found it's not okay as
> the code depends on the value being set correctly:
>
> ==> 36...