[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220518090830.59ab629f@kernel.org>
Date: Wed, 18 May 2022 09:08:30 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Felix Fietkau <nbd@....name>
Cc: Lorenzo Bianconi <lorenzo@...nel.org>, netdev@...r.kernel.org,
john@...ozen.org, sean.wang@...iatek.com, Mark-MC.Lee@...iatek.com,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
Sam.Shih@...iatek.com, linux-mediatek@...ts.infradead.org,
devicetree@...r.kernel.org, robh@...nel.org,
lorenzo.bianconi@...hat.com
Subject: Re: [PATCH v2 net-next 12/15] net: ethernet: mtk_eth_soc: introduce
MTK_NETSYS_V2 support
On Wed, 18 May 2022 17:50:12 +0200 Felix Fietkau wrote:
> On 18.05.22 17:47, Jakub Kicinski wrote:
> >> I used this approach just to be aligned with current codebase:
> >> https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/mediatek/mtk_eth_soc.c#L1006
> >> https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/mediatek/mtk_eth_soc.c#L1031
> >>
> >> but I guess we can even convert the code to use barrier instead. Agree?
> >
> > Oh, I didn't realize. No preference on converting the old code
> > but it looks like a cargo cult to me so in the new code let's
> > not WRITE_ONCE() all descriptor writes unless there's a reason.
> If I remember correctly, the existing places use WRITE_ONCE to prevent
> write tearing to uncached memory.
Okay, makes sense then.
Powered by blists - more mailing lists