On Thu, May 01, 2025 at 05:02:59PM -0500, Bjorn Helgaas wrote: > On Fri, Mar 21, 2025 at 05:39:30PM -0500, Bjorn Helgaas wrote: > > On Fri, Mar 21, 2025 at 03:16:48PM -0700, Paul E. McKenney wrote: > > > On Fri, Mar 21, 2025 at 05:01:15PM -0500, Bjorn Helgaas wrote: > > > > On Thu, Mar 20, 2025 at 06:58:03PM -0700, Jon Pan-Doh wrote: > > > > > Update name to reflect the broader definition of structs/variables that > > > > > are stored (e.g. ratelimits). This is a preparatory patch for adding rate > > > > > limit support. > > > > > > > > > > Signed-off-by: Karolina Stolarek <karolina.stolarek@xxxxxxxxxx> > > > > > Signed-off-by: Jon Pan-Doh <pandoh@xxxxxxxxxx> > > > > > Reported-by: Sargun Dhillon <sargun@xxxxxxxx> > > > > > > > > What did Sargun report? Is there a bug fix in here? Can we include a > > > > URL to whatever Sargun reported? > > > > > > He reported RCU CPU stall warnings and CSD-lock warnings internally > > > within Meta, so sorry, no useful URL. > > CSD? I guess knowing what CSD is isn't completely essential here, but > I haven't a clue what it means. Something to do with IPI and getting > another CPU to run a function? Is CSD an acronym for something? Yeah, it is a bit obscure, apologies! It is "CSD" as in the csd_lock() function, and it stands for "call single data", as in the ->csd field of the call_function_data structure, which is of type call_single_data_t. All in the service of smp_call_function() and friends, mostly in the file kernel/smp.c. Thanx, Paul
