From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Ben Hutchings <ben.hutchings@essensium.com>
Cc: "David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>, <linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
<linux-omap@vger.kernel.org>, Lokesh Vutla <lokeshvutla@ti.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH net] net: ethernet: ti: cpsw: fix min eth packet size for non-switch use-cases
Date: Fri, 11 Jun 2021 23:52:53 +0300 [thread overview]
Message-ID: <7d41dc85-ba44-ff46-8c53-019f97e0703d@ti.com> (raw)
In-Reply-To: <20210611175448.GA25728@cephalopod>
On 11/06/2021 20:54, Ben Hutchings wrote:
> On Fri, Jun 11, 2021 at 04:27:32PM +0300, Grygorii Strashko wrote:
> [...]
>> --- a/drivers/net/ethernet/ti/cpsw_new.c
>> +++ b/drivers/net/ethernet/ti/cpsw_new.c
>> @@ -918,14 +918,17 @@ static netdev_tx_t cpsw_ndo_start_xmit(struct sk_buff *skb,
>> struct cpts *cpts = cpsw->cpts;
>> struct netdev_queue *txq;
>> struct cpdma_chan *txch;
>> + unsigned int len;
>> int ret, q_idx;
>>
>> - if (skb_padto(skb, CPSW_MIN_PACKET_SIZE)) {
>> + if (skb_padto(skb, priv->tx_packet_min)) {
>> cpsw_err(priv, tx_err, "packet pad failed\n");
>> ndev->stats.tx_dropped++;
>> return NET_XMIT_DROP;
>> }
>>
>> + len = skb->len < priv->tx_packet_min ? priv->tx_packet_min : skb->len;
>> +
>> if (skb_shinfo(skb)->tx_flags & SKBTX_HW_TSTAMP &&
>> priv->tx_ts_enabled && cpts_can_timestamp(cpts, skb))
>> skb_shinfo(skb)->tx_flags |= SKBTX_IN_PROGRESS;
>> @@ -937,7 +940,7 @@ static netdev_tx_t cpsw_ndo_start_xmit(struct sk_buff *skb,
>> txch = cpsw->txv[q_idx].ch;
>> txq = netdev_get_tx_queue(ndev, q_idx);
>> skb_tx_timestamp(skb);
>> - ret = cpdma_chan_submit(txch, skb, skb->data, skb->len,
>> + ret = cpdma_chan_submit(txch, skb, skb->data, len,
>> priv->emac_port);
>> if (unlikely(ret != 0)) {
>> cpsw_err(priv, tx_err, "desc submit failed\n");
>
> This change is odd because cpdma_chan_submit() already pads the DMA
> length.
>
> Would it not make more sense to update cpdma_params::min_packet_size
> instead of adding a second minimum?
i've been thinking about it, but cpdma parameter copied into cpdma context once at probe,
so change will be more complex.
Can be done if you insist.
>
> [...]
>> @@ -1686,6 +1690,7 @@ static int cpsw_dl_switch_mode_set(struct devlink *dl, u32 id,
>>
>> priv = netdev_priv(sl_ndev);
>> slave->port_vlan = vlan;
>> + priv->tx_packet_min = CPSW_MIN_PACKET_SIZE_VLAN;
>> if (netif_running(sl_ndev))
>> cpsw_port_add_switch_def_ale_entries(priv,
>> slave);
>> @@ -1714,6 +1719,7 @@ static int cpsw_dl_switch_mode_set(struct devlink *dl, u32 id,
>>
>> priv = netdev_priv(slave->ndev);
>> slave->port_vlan = slave->data->dual_emac_res_vlan;
>> + priv->tx_packet_min = CPSW_MIN_PACKET_SIZE;
>> cpsw_port_add_dual_emac_def_ale_entries(priv, slave);
>> }
>>
> [...]
>
> What happens if this races with the TX path? Should there be a
> netif_tx_lock() / netif_tx_unlock() around this change?
Mode change operation is heavy and expected to be done once when bridge is configured.
It will completely wipe out all ALE entries and so all VLAN setting -
which any way need to be configured (reconfigured) during bridge configuration.
So, traffic can be disturbed during mode change operation.
As result, in my opinion, it make no sense to add additional complexity here.
--
Best regards,
grygorii
prev parent reply other threads:[~2021-06-11 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 13:27 Grygorii Strashko
2021-06-11 17:54 ` Ben Hutchings
2021-06-11 20:52 ` Grygorii Strashko [this message]
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=7d41dc85-ba44-ff46-8c53-019f97e0703d@ti.com \
--to=grygorii.strashko@ti.com \
--cc=ben.hutchings@essensium.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®