[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <713182b5-5fda-48a7-8947-8dc3d10c42b1@davidwei.uk>
Date: Mon, 20 May 2024 10:27:01 -0700
From: David Wei <dw@...idwei.uk>
To: Ziwei Xiao <ziweixiao@...gle.com>
Cc: netdev@...r.kernel.org, jeroendb@...gle.com, pkaligineedi@...gle.com,
shailend@...gle.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, willemb@...gle.com,
hramamurthy@...gle.com, rushilg@...gle.com, jfraker@...gle.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 4/5] gve: Add flow steering adminq commands
On 2024-05-09 17:18, Ziwei Xiao wrote:
> On Tue, May 7, 2024 at 11:24 PM David Wei <dw@...idwei.uk> wrote:
>>
>> On 2024-05-07 15:59, Ziwei Xiao wrote:
[...]
>>> +/* Flow-steering related definitions */
>>> +enum gve_adminq_flow_rule_cfg_opcode {
>>> + GVE_RULE_ADD = 0,
>>> + GVE_RULE_DEL = 1,
>>> + GVE_RULE_RESET = 2,
>>> +};
>>
>> Could these be more descriptive?
>>
> Could you be more specific on which needs to be improved? Is the enum
> name or the field name?
Sorry for the late response.
The enum field names. GVE_RULE_x is too sparse for me; what rule? To
match the rest of the file maybe something like GVE_FLOW_RULE_CFG_x.
Powered by blists - more mailing lists