[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230315225046.3cfed1ee@gandalf.local.home>
Date: Wed, 15 Mar 2023 22:50:46 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Joel Fernandes <joel@...lfernandes.org>
Cc: Uladzislau Rezki <urezki@...il.com>, Jens Axboe <axboe@...nel.dk>,
LKML <linux-kernel@...r.kernel.org>, RCU <rcu@...r.kernel.org>,
"Paul E . McKenney" <paulmck@...nel.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@...y.com>,
Philipp Reisner <philipp.reisner@...bit.com>,
Bryan Tan <bryantan@...are.com>,
Eric Dumazet <edumazet@...gle.com>,
Bob Pearson <rpearsonhpe@...il.com>,
Ariel Levkovich <lariel@...dia.com>,
"Theodore Ts'o" <tytso@....edu>, Julian Anastasov <ja@....bg>
Subject: Re: [PATCH 00/13] Rename k[v]free_rcu() single argument to
k[v]free_rcu_mightsleep()
On Wed, 15 Mar 2023 22:13:26 -0400
Joel Fernandes <joel@...lfernandes.org> wrote:
> > Why not call it kvfree_rcu_alloc() ? It allocates right?
>
> Sure, but one can say now that allocating is an implementation detail? ;-)
I was being sarcastic.
But as the mighty Linus once said: "In the Internet, nobody can hear your sarcasm"
-- Steve
Powered by blists - more mailing lists