[net-next,06/20] net: hns3: Modify the update period of packet statistics

From: Jian Shen <shenjian15@huawei.com>

It takes more than 200 query response messages between
driver and IMP, while updating the packet statistics.
It's too heavy for IMP to update it per second.

Extend the update period of packet statistics data from
1 second to 300 seconds(if too long, the statistics may
overflow).

As a result, we need to update it while querying with
ifconfig tool to keep the statistics data fresh.

Signed-off-by: Jian Shen <shenjian15@huawei.com>
Signed-off-by: Peng Li <lipeng321@huawei.com>
---
 drivers/net/ethernet/hisilicon/hns3/hns3_enet.c         |  3 +++
 drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c | 12 +++++++++++-
 drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.h |  3 +++
 3 files changed, 17 insertions(+), 1 deletion(-)

> --- a/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c
> +++ b/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c
> @@ -1126,6 +1126,7 @@ static int hns3_nic_set_features(struct net_device *netdev,
>  {
>  	struct hns3_nic_priv *priv = netdev_priv(netdev);
>  	int queue_num = priv->ae_handle->kinfo.num_tqps;
> +	struct hnae3_handle *handle = priv->ae_handle;
>  	struct hns3_enet_ring *ring;
>  	unsigned int start;
>  	unsigned int idx;
> @@ -1134,6 +1135,8 @@ static int hns3_nic_set_features(struct net_device *netdev,
>  	u64 tx_pkts = 0;
>  	u64 rx_pkts = 0;
>  
> +	handle->ae_algo->ops->update_stats(handle, &netdev->stats);
> +
>  	for (idx = 0; idx < queue_num; idx++) {
>  		/* fetch the tx stats */
>  		ring = priv->ring_data[idx].ring;

There is something odd going on with patch here. Notice how it says
hns3_nic_set_features(). This is not the function being patched, it is
actually the next one, hns3_nic_get_stats64(), which makes a lot more
sense.

Is it because the static void is on the previous line?

It would be nice if the function was correctly reported. It makes it
easier to review the patch.

       Andrew

On 2018/1/5 22:54, Andrew Lunn wrote:
>> --- a/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c
>> +++ b/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c
>> @@ -1126,6 +1126,7 @@ static int hns3_nic_set_features(struct net_device *netdev,
>>   {
>>   	struct hns3_nic_priv *priv = netdev_priv(netdev);
>>   	int queue_num = priv->ae_handle->kinfo.num_tqps;
>> +	struct hnae3_handle *handle = priv->ae_handle;
>>   	struct hns3_enet_ring *ring;
>>   	unsigned int start;
>>   	unsigned int idx;
>> @@ -1134,6 +1135,8 @@ static int hns3_nic_set_features(struct net_device *netdev,
>>   	u64 tx_pkts = 0;
>>   	u64 rx_pkts = 0;
>>   
>> +	handle->ae_algo->ops->update_stats(handle, &netdev->stats);
>> +
>>   	for (idx = 0; idx < queue_num; idx++) {
>>   		/* fetch the tx stats */
>>   		ring = priv->ring_data[idx].ring;
> There is something odd going on with patch here. Notice how it says
> hns3_nic_set_features(). This is not the function being patched, it is
> actually the next one, hns3_nic_get_stats64(), which makes a lot more
> sense.
>
> Is it because the static void is on the previous line?
Yes, it is because the static void is on the previous line.

I can add one patch to fix the  previous line ,  and this patch will 
correct  automatically.

do it need V2 patchset? or push a new patch after this patchset?

>
> It would be nice if the function was correctly reported. It makes it
> easier to review the patch.
>
>         Andrew
>
> .
>

> >Is it because the static void is on the previous line?
> Yes, it is because the static void is on the previous line.
> 
> I can add one patch to fix the  previous line ,  and this patch will correct
> automatically.
> 
> do it need V2 patchset? or push a new patch after this patchset?

Thanks for looking into this. This actually seems like a patch bug,
but i think the consensus is to have the function type on the same
line as the function name within Linux.

No need for a v2. Just send followup patches.

   Andrew