From: Ioana Ciornei <ciorneiioana@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Ioana Ciornei <ciorneiioana@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: Re: [RFC 5/9] staging: dpaa2-switch: handle Rx path on control interface
Date: Thu, 5 Nov 2020 13:22:58 +0200 [thread overview]
Message-ID: <20201105112258.sgbr2fq66u47vokr@skbuf> (raw)
In-Reply-To: <20201105004516.GG933237@lunn.ch>
On Thu, Nov 05, 2020 at 01:45:16AM +0100, Andrew Lunn wrote:
> > +/* Manage all NAPI instances for the control interface.
> > + *
> > + * We only have one RX queue and one Tx Conf queue for all
> > + * switch ports. Therefore, we only need to enable the NAPI instance once, the
> > + * first time one of the switch ports runs .dev_open().
> > + */
> > +
> > +static void dpaa2_switch_enable_ctrl_if_napi(struct ethsw_core *ethsw)
> > +{
> > + int i;
> > +
> > + /* a new interface is using the NAPI instance */
> > + ethsw->napi_users++;
> > +
> > + /* if there is already a user of the instance, return */
> > + if (ethsw->napi_users > 1)
> > + return;
>
> Does there need to be any locking here? Or does it rely on RTNL?
> Maybe a comment would be nice, or a check that RTNL is actually held.
>
It relies on the RTNL. I'll add an assert on the RTNL lock and a comment
to go with that.
> > +
> > + if (!dpaa2_switch_has_ctrl_if(ethsw))
> > + return;
> > +
> > + for (i = 0; i < DPAA2_SWITCH_RX_NUM_FQS; i++)
> > + napi_enable(ðsw->fq[i].napi);
> > +}
>
> > +static void dpaa2_switch_rx(struct dpaa2_switch_fq *fq,
> > + const struct dpaa2_fd *fd)
> > +{
> > + struct ethsw_core *ethsw = fq->ethsw;
> > + struct ethsw_port_priv *port_priv;
> > + struct net_device *netdev;
> > + struct vlan_ethhdr *hdr;
> > + struct sk_buff *skb;
> > + u16 vlan_tci, vid;
> > + int if_id = -1;
> > + int err;
> > +
> > + /* prefetch the frame descriptor */
> > + prefetch(fd);
>
> Does this actually do any good, given that the next call:
>
> > +
> > + /* get switch ingress interface ID */
> > + if_id = upper_32_bits(dpaa2_fd_get_flc(fd)) & 0x0000FFFF;
>
> is accessing the frame descriptor? The idea of prefetch is to let it
> bring it into the cache while you are busy doing something else,
> hopefully with something which is already cache hot.
>
I'll check w and w/o the prefetch but, most probably, it doesn't help.
Thanks.
Ioana
next prev parent reply other threads:[~2020-11-05 11:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 16:57 [RFC 0/9] staging: dpaa2-switch: add support for CPU terminated traffic Ioana Ciornei
2020-11-04 16:57 ` [RFC 1/9] staging: dpaa2-switch: get control interface attributes Ioana Ciornei
2020-11-04 16:57 ` [RFC 2/9] staging: dpaa2-switch: setup buffer pool for control traffic Ioana Ciornei
2020-11-04 16:57 ` [RFC 3/9] staging: dpaa2-switch: setup RX path rings Ioana Ciornei
2020-11-04 16:57 ` [RFC 4/9] staging: dpaa2-switch: setup dpio Ioana Ciornei
2020-11-04 16:57 ` [RFC 5/9] staging: dpaa2-switch: handle Rx path on control interface Ioana Ciornei
2020-11-05 0:45 ` Andrew Lunn
2020-11-05 11:22 ` Ioana Ciornei [this message]
2020-11-04 16:57 ` [RFC 6/9] staging: dpaa2-switch: add .ndo_start_xmit() callback Ioana Ciornei
2020-11-04 21:27 ` Vladimir Oltean
2020-11-05 8:11 ` Ioana Ciornei
2020-11-05 1:04 ` Andrew Lunn
2020-11-05 8:25 ` Ioana Ciornei
2020-11-05 13:45 ` Andrew Lunn
2020-11-05 15:51 ` Ioana Ciornei
2020-11-04 16:57 ` [RFC 7/9] staging: dpaa2-switch: enable the control interface Ioana Ciornei
2020-11-04 16:57 ` [RFC 8/9] staging: dpaa2-switch: properly setup switching domains Ioana Ciornei
2020-11-04 22:08 ` Vladimir Oltean
2020-11-05 10:58 ` Ioana Ciornei
2020-11-04 16:57 ` [RFC 9/9] staging: dpaa2-switch: accept only vlan-aware upper devices Ioana Ciornei
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=20201105112258.sgbr2fq66u47vokr@skbuf \
--to=ciorneiioana@gmail.com \
--cc=andrew@lunn.ch \
--cc=gregkh@linuxfoundation.org \
--cc=ioana.ciornei@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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