Displaying 3 results from an estimated 3 matches for "persist0x100".
2020 Sep 22
2
consuming pre-created tap - with multiqueue
...mestamp":"2020-09-22T10:34:29.335000Z"}
I do not understand how it can try to set the VNET_HDR flag, since I
have not set it when I created it, which, as per [0] should only
happen when requested. Here's the tap device I'm creating: (output of
`ip tuntap show`)
- tap0: tap persist0x100 user 107 group 107
I'm confused by this, since on [1] it says that only one flag can be
used (persist *or* vnet_hdr). Also, from my limited understanding, in
order to open a pre-created tap device, it must be set to persistent.
Am I right (in the sense that these flags cannot co-exist) ? If s...
2020 Sep 23
1
Re: consuming pre-created tap - with multiqueue
...>
> > I do not understand how it can try to set the VNET_HDR flag, since I
> > have not set it when I created it, which, as per [0] should only
> > happen when requested. Here's the tap device I'm creating: (output of
> > `ip tuntap show`)
> > - tap0: tap persist0x100 user 107 group 107
>
> IIUC the kernel code correctly, the VNET_HDR flag is not required
> to be set when you first create the tap device - it appears to be
> permitted any time you open a file descriptor for it.
>
> AFAIK, there is no problem with VNET_HDR, as it is a standard...
2020 Sep 23
0
Re: consuming pre-created tap - with multiqueue
...T10:34:29.335000Z"}
>
> I do not understand how it can try to set the VNET_HDR flag, since I
> have not set it when I created it, which, as per [0] should only
> happen when requested. Here's the tap device I'm creating: (output of
> `ip tuntap show`)
> - tap0: tap persist0x100 user 107 group 107
IIUC the kernel code correctly, the VNET_HDR flag is not required
to be set when you first create the tap device - it appears to be
permitted any time you open a file descriptor for it.
AFAIK, there is no problem with VNET_HDR, as it is a standard flag
we've set on all tap...