[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <afe22a46-1cc4-469a-9935-c76cfcea5842@lunn.ch>
Date: Tue, 26 Mar 2024 16:33:17 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Johannes Berg <johannes@...solutions.net>, netdev@...r.kernel.org
Subject: Re: [PATCH 0/3] using guard/__free in networking
On Mon, Mar 25, 2024 at 07:09:57PM -0700, Jakub Kicinski wrote:
> On Mon, 25 Mar 2024 23:31:25 +0100 Johannes Berg wrote:
> > Hi,
> >
> > So I started playing with this for wifi, and overall that
> > does look pretty nice, but it's a bit weird if we can do
> >
> > guard(wiphy)(&rdev->wiphy);
> >
> > or so, but still have to manually handle the RTNL in the
> > same code.
>
> Dunno, it locks code instead of data accesses.
> Forgive the comparison but it feels too much like Java to me :)
> scoped_guard is fine, the guard() not so much.
I tend to agree. guard() does not feel like C. scoped_guard does.
Andrew
Powered by blists - more mailing lists