[PATCH next 4/7] vmxnet3: add command to set ring buffer sizes
Ferruh Yigit
ferruh.yigit at amd.com
Thu Apr 27 10:50:39 CEST 2023
On 4/26/2023 6:27 PM, Ronak Doshi wrote:
>
>
> On 4/26/23, 9:58 AM, "Ferruh Yigit" <ferruh.yigit at amd.com <mailto:ferruh.yigit at amd.com>> wrote:
>
>> As far as I can see these "vmware_pack_begin.h" & "vmware_pack_end.h"
>> has only file license comment, and I can see this is used in a few other
>> type declaration.
>>
>> What is the reasoning behind using these headers?
>
> This has been the case since driver was added to dpdk. The information is present in README.
> I did not want to change the format being used for the declarations in the driver.
>
README doesn't say much.
The usage is not standard, and intention is not clear.
Can you please dig this issue more to learn the the intention, may be we
can find a better way or get rid of them completely?
Just to record, usage is:
typedef
#include "vmware_pack_begin.h"
struct Vmxnet3_RingBufferSize {
__le16 ring1BufSizeType0;
__le16 ring1BufSizeType1;
__le16 ring2BufSizeType1;
__le16 pad;
}
#include "vmware_pack_end.h"
Vmxnet3_RingBufferSize;
Content of "vmware_pack_begin.h":
```
/* SPDX-License-Identifier: BSD-3-Clause
* Copyright(c) 2010-2014 Intel Corporation
*/
```
"vmware_pack_end.h":
```
/* SPDX-License-Identifier: BSD-3-Clause
* Copyright(c) 2010-2014 Intel Corporation
*/
```
More information about the dev
mailing list