netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Justin Lai <justinlai0215@realtek.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"andrew@lunn.ch" <andrew@lunn.ch>,
	"jiri@resnulli.us" <jiri@resnulli.us>,
	"horms@kernel.org" <horms@kernel.org>,
	"rkannoth@marvell.com" <rkannoth@marvell.com>,
	"jdamato@fastly.com" <jdamato@fastly.com>,
	Ping-Ke Shih <pkshih@realtek.com>,
	Larry Chiu <larry.chiu@realtek.com>
Subject: RE: [PATCH net-next v26 07/13] rtase: Implement a function to receive packets
Date: Fri, 9 Aug 2024 06:43:38 +0000	[thread overview]
Message-ID: <1f846891e9264b94bf00cb934dd83d2a@realtek.com> (raw)
In-Reply-To: <20240808200705.0e77147c@kernel.org>

> On Wed, 7 Aug 2024 11:37:17 +0800 Justin Lai wrote:
> > +static int rx_handler(struct rtase_ring *ring, int budget) {
> > +     union rtase_rx_desc *desc_base = ring->desc;
> > +     u32 pkt_size, cur_rx, delta, entry, status;
> > +     struct rtase_private *tp = ring->ivec->tp;
> > +     struct net_device *dev = tp->dev;
> > +     union rtase_rx_desc *desc;
> > +     struct sk_buff *skb;
> > +     int workdone = 0;
> > +
> > +     cur_rx = ring->cur_idx;
> > +     entry = cur_rx % RTASE_NUM_DESC;
> > +     desc = &desc_base[entry];
> > +
> > +     do {
> > +             /* make sure discriptor has been updated */
> > +             dma_rmb();
> 
> I think I already asked, but this still makes no sense to me.
> dma barriers are between accesses to descriptors.
> dma_rmb() ensures ordering of two reads.
> Because modern CPUs can perform reads out of order.
> What two reads is this barrier ordering?
> 
> Please read the doc on memory barriers relating to dma.
> I think this is in the wrong place.
> 
> r8169 gets it right.

Thank you for your reply. I will modify it.

Thanks
Justin
> 
> > +             status = le32_to_cpu(desc->desc_status.opts1);
> > +
> > +             if (status & RTASE_DESC_OWN)
> > +                     break;
> > +


  reply	other threads:[~2024-08-09  6:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07  3:37 [PATCH net-next v26 00/13] Add Realtek automotive PCIe driver Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 01/13] rtase: Add support for a pci table in this module Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 02/13] rtase: Implement the .ndo_open function Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 03/13] rtase: Implement the rtase_down function Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 04/13] rtase: Implement the interrupt routine and rtase_poll Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 05/13] rtase: Implement hardware configuration function Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 06/13] rtase: Implement .ndo_start_xmit function Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 07/13] rtase: Implement a function to receive packets Justin Lai
2024-08-09  3:07   ` Jakub Kicinski
2024-08-09  6:43     ` Justin Lai [this message]
2024-08-07  3:37 ` [PATCH net-next v26 08/13] rtase: Implement net_device_ops Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 09/13] rtase: Implement pci_driver suspend and resume function Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 10/13] rtase: Implement ethtool function Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 11/13] rtase: Add a Makefile in the rtase folder Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 12/13] realtek: Update the Makefile and Kconfig in the realtek folder Justin Lai
2024-08-07  3:37 ` [PATCH net-next v26 13/13] MAINTAINERS: Add the rtase ethernet driver entry Justin Lai

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=1f846891e9264b94bf00cb934dd83d2a@realtek.com \
    --to=justinlai0215@realtek.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jdamato@fastly.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=larry.chiu@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pkshih@realtek.com \
    --cc=rkannoth@marvell.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;
as well as URLs for NNTP newsgroup(s).