From: "Hawkins, Nick" <nick.hawkins@hpe.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "christophe.jaillet@wanadoo.fr" <christophe.jaillet@wanadoo.fr>,
"simon.horman@corigine.com" <simon.horman@corigine.com>,
"Verdun, Jean-Marie" <verdun@hpe.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v3 4/5] net: hpe: Add GXP UMAC Driver
Date: Thu, 17 Aug 2023 19:19:55 +0000 [thread overview]
Message-ID: <DM4PR84MB1927C6684845A9AEBD9F934F881AA@DM4PR84MB1927.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <01e96219-4f0c-4259-9398-bc2e6bc1794f@lunn.ch>
Hi Andrew,
> > +static int umac_init_hw(struct net_device *ndev)
> > +{
> > + } else {
> > + value |= UMAC_CFG_FULL_DUPLEX;
> > +
> > + if (ndev->phydev->speed == SPEED_1000) {
> I'm pretty sure i pointed this out once before. It is not safe to
> access phydev members outside of the adjust link callback.
My mistake I missed this phydev member access. I will rely on
the adjust link callback to configure it.
> > +static int umac_start_xmit(struct sk_buff *skb, struct net_device *ndev)
> > +{
> > + struct umac_priv *umac = netdev_priv(ndev);
> > + struct umac_tx_desc_entry *ptxdesc;
> > + unsigned int length;
> > + u8 *pframe;
> > +
> > + ptxdesc = &umac->tx_descs->entrylist[umac->tx_cur];
> > + pframe = umac->tx_descs->framelist[umac->tx_cur];
> > +
> > + length = skb->len;
> > + if (length > 1514) {
> > + netdev_err(ndev, "send data %d bytes > 1514, clamp it to 1514\n",
> > + skb->len);
> Than should be rate limited.
How is this done? Is there a particular function to call that
will handle it in the backend?
I thought the rate limiting is happening in this
function already below at:
/* if current tx ring buffer is full, stop the queue */
ptxdesc = &umac->tx_descs->entrylist[umac->tx_cur];
if (ptxdesc->status & UMAC_RING_ENTRY_HW_OWN)
netif_stop_queue(ndev);
> Also, if you chop the end of the packet, it is going to be useless. It
> is better to drop it, to improve your goodput.
I will drop it.
Thanks,
-Nick Hawkins
next prev parent reply other threads:[~2023-08-17 19:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 21:52 [PATCH v3 0/5] ARM: Add GXP UMAC Support nick.hawkins
2023-08-16 21:52 ` [PATCH v3 1/5] dt-bindings: net: Add HPE GXP UMAC MDIO nick.hawkins
2023-08-17 1:10 ` Andrew Lunn
2023-08-16 21:52 ` [PATCH v3 2/5] net: hpe: Add " nick.hawkins
2023-08-17 1:19 ` Andrew Lunn
2023-08-16 21:52 ` [PATCH v3 3/5] dt-bindings: net: Add HPE GXP UMAC nick.hawkins
2023-08-17 8:53 ` Conor Dooley
2023-08-16 21:52 ` [PATCH v3 4/5] net: hpe: Add GXP UMAC Driver nick.hawkins
2023-08-17 1:46 ` Andrew Lunn
2023-08-17 19:19 ` Hawkins, Nick [this message]
2023-08-17 19:44 ` Andrew Lunn
2023-08-18 20:11 ` Hawkins, Nick
2023-08-18 21:15 ` Andrew Lunn
2023-08-22 19:00 ` Hawkins, Nick
2023-08-22 20:00 ` Andrew Lunn
2023-08-25 18:54 ` Hawkins, Nick
2023-09-04 3:58 ` Andrew Lunn
2023-09-11 21:12 ` Hawkins, Nick
2023-09-12 23:52 ` Andrew Lunn
2023-08-17 7:45 ` Simon Horman
2023-08-16 21:52 ` [PATCH v3 5/5] MAINTAINERS: HPE: Add GXP UMAC Networking Files nick.hawkins
2023-08-17 1:47 ` Andrew Lunn
2023-08-17 1:08 ` [PATCH v3 0/5] ARM: Add GXP UMAC Support Andrew Lunn
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=DM4PR84MB1927C6684845A9AEBD9F934F881AA@DM4PR84MB1927.NAMPRD84.PROD.OUTLOOK.COM \
--to=nick.hawkins@hpe.com \
--cc=andrew@lunn.ch \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=simon.horman@corigine.com \
--cc=verdun@hpe.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