Netdev List
 help / color / mirror / Atom feed
From: Fan Gong <gongfan1@huawei.com>
To: <mohsin.bashr@gmail.com>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
	<dimitri.daskalakis1@gmail.com>, <edumazet@google.com>,
	<gongfan1@huawei.com>, <guoxin09@huawei.com>, <horms@kernel.org>,
	<hramamurthy@google.com>, <ioana.ciornei@nxp.com>,
	<kuba@kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <luosifu@huawei.com>,
	<maxime.chevallier@bootlin.com>, <netdev@vger.kernel.org>,
	<pabeni@redhat.com>, <shijing34@huawei.com>,
	<tengpeisen@huawei.com>, <wudi234@huawei.com>,
	<wulike1@huawei.com>, <zhengjiezhen@h-partners.com>,
	<zhoushuai28@huawei.com>, <august.hewei@huawei.com>
Subject: Re: Re: [PATCH net-next v11 1/5] hinic3: Add ethtool queue ops
Date: Thu, 23 Jul 2026 09:32:19 +0800	[thread overview]
Message-ID: <20260723013219.797-1-gongfan1@huawei.com> (raw)
In-Reply-To: <c4473a79-567a-430b-b463-f45d4ef3ea28@gmail.com>

> >    Implement following ethtool callback function:
> > .get_ringparam
> > .set_ringparam
> >
> >    These callbacks allow users to utilize ethtool for detailed
> > queue depth configuration and monitoring.
> >
> >    Change port_state_mutex to state_lock as a unified mutex lock
> > in hinic3_nic_dev.
> >
> >    Tightens the success criterion for hinic3_rx_fill_buffers() in
> > hinic3_configure_rxqs().
> >
> >    Changes hinic3_tx_csum()/hinic3_tx_offload() to propagate
> > skb_checksum_help() failures into a TX drop.
> >
> >    Renames hinic3_uninit_qps() to hinic3_get_cur_qps().
> >
> >    Splits hinic3_open_channel() into hinic3_prepare_channel() and
> > hinic3_open_channel().
> >
>
> It may just be me, but I feel like there is a lot going in this single
> patch. Ideally, a patch should carry one logical change. This patch is
> doing 3 things: refactor, new code, bug-fixing in the hinic3_close() path.

Thanks for the following 3 review comments. We are pushing new codes to the
net-next. However, fixing review comments leads to some refactoring and
bug-fixing codes.

We are considering split patch #1 into smaller ones in the next patchset.

> > @@ -330,6 +330,8 @@ static void hinic3_link_status_change(struct net_device *netdev,
> >   		netif_carrier_off(netdev);
> >   		netdev_dbg(netdev, "Link is down\n");
> >   	}
> > +
> > +	return;
>
> Unrelated?

Sorry for our negligence. We will remove this unrelated change in the next
patchset.

> > @@ -493,10 +580,15 @@ static int hinic3_close(struct net_device *netdev)
> >   		return 0;
> >   	}
> >
> > +	mutex_lock(&nic_dev->state_lock);
> >   	hinic3_vport_down(netdev);
> >   	hinic3_close_channel(netdev);
> > -	hinic3_uninit_qps(nic_dev, &qp_params);
> > -	hinic3_free_channel_resources(netdev, &qp_params, &nic_dev->q_params);
> > +	hinic3_get_cur_qps(nic_dev, &qp_params);
> > +	hinic3_free_channel_resources(netdev, &qp_params,
> > +				      &nic_dev->q_params);
> > +	hinic3_free_nicio_res(nic_dev);
> > +	hinic3_destroy_num_qps(netdev);
>
> free_nicio_res(), and destroy_num_qps() looks like fixes to me on the
> clean-up path. Should these go to the net tree?

As mentioned above, we reckon it as a necessary fix to commit new codes, thus
we put it in this patch.

  reply	other threads:[~2026-07-23  1:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 12:53 [PATCH net-next v11 0/5] net: hinic3: PF initialization Fan Gong
2026-07-20 12:53 ` [PATCH net-next v11 1/5] hinic3: Add ethtool queue ops Fan Gong
2026-07-21 18:07   ` Mohsin Bashir
2026-07-23  1:32     ` Fan Gong [this message]
2026-07-20 12:53 ` [PATCH net-next v11 2/5] hinic3: Add ethtool statistic ops Fan Gong
2026-07-21 19:21   ` Dimitri Daskalakis
2026-07-23  1:35     ` Fan Gong
2026-07-20 12:53 ` [PATCH net-next v11 3/5] hinic3: Add ethtool coalesce ops Fan Gong
2026-07-20 12:53 ` [PATCH net-next v11 4/5] hinic3: Add ethtool rss ops Fan Gong
2026-07-20 12:53 ` [PATCH net-next v11 5/5] hinic3: Remove unneeded coalesce parameters Fan Gong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260723013219.797-1-gongfan1@huawei.com \
    --to=gongfan1@huawei.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=august.hewei@huawei.com \
    --cc=davem@davemloft.net \
    --cc=dimitri.daskalakis1@gmail.com \
    --cc=edumazet@google.com \
    --cc=guoxin09@huawei.com \
    --cc=horms@kernel.org \
    --cc=hramamurthy@google.com \
    --cc=ioana.ciornei@nxp.com \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luosifu@huawei.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mohsin.bashr@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shijing34@huawei.com \
    --cc=tengpeisen@huawei.com \
    --cc=wudi234@huawei.com \
    --cc=wulike1@huawei.com \
    --cc=zhengjiezhen@h-partners.com \
    --cc=zhoushuai28@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox