[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200827124404.496ff40b@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Thu, 27 Aug 2020 12:44:04 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Luo bin <luobin9@...wei.com>
Cc: <davem@...emloft.net>, <linux-kernel@...r.kernel.org>,
<netdev@...r.kernel.org>, <luoxianjun@...wei.com>,
<yin.yinshi@...wei.com>, <cloud.wangxiaoyun@...wei.com>,
<chiqijun@...wei.com>
Subject: Re: [PATCH net-next v1 3/3] hinic: add support to query function
table
On Thu, 27 Aug 2020 19:13:21 +0800 Luo bin wrote:
> + switch (idx) {
> + case VALID:
> + return funcfg_table_elem->dw0.bs.valid;
> + case RX_MODE:
> + return funcfg_table_elem->dw0.bs.nic_rx_mode;
> + case MTU:
> + return funcfg_table_elem->dw1.bs.mtu;
> + case VLAN_MODE:
> + return funcfg_table_elem->dw1.bs.vlan_mode;
> + case VLAN_ID:
> + return funcfg_table_elem->dw1.bs.vlan_id;
> + case RQ_DEPTH:
> + return funcfg_table_elem->dw13.bs.cfg_rq_depth;
> + case QUEUE_NUM:
> + return funcfg_table_elem->dw13.bs.cfg_q_num;
The first two patches look fairly unobjectionable to me, but here the
information does not seem that driver-specific. What's vlan_mode, and
vlan_id in the context of PF? Why expose mtu, is it different than
netdev mtu? What's valid? rq_depth?
Powered by blists - more mailing lists