Page MenuHomeFreeBSD

sched_4bsd: rename runq to runq_global
ClosedPublic

Authored by mchoo on Jul 6 2026, 10:24 PM.
Tags
None
Referenced Files
F167334279: D58065.diff
Fri, Aug 21, 12:07 AM
Unknown Object (File)
Tue, Aug 18, 5:56 AM
Unknown Object (File)
Sun, Aug 16, 4:38 PM
Unknown Object (File)
Fri, Aug 14, 5:01 PM
Unknown Object (File)
Sun, Aug 9, 9:45 AM
Unknown Object (File)
Sun, Aug 9, 5:15 AM
Unknown Object (File)
Sat, Aug 8, 10:47 PM
Unknown Object (File)
Sat, Aug 8, 6:27 PM
Subscribers

Details

Summary

In upcoming changes, 'struct td_sched' will store CPU ID of the thread's
current runqueue instead of a pointer to the runqueue. This requires
functions to store pointer to the runqueue as a local variable. Although
the name 'runq' seams ideal for these local variables, it is already
taken by the global runqueue. Thus rename the global runqueue to
'runq_global' to hint the variable is the global runqueue and yield the
name 'runq' to local variables.

Suggested by: olce

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

mchoo requested review of this revision.Jul 6 2026, 10:24 PM

Looks much better like that. :-) "Suggested by: olce" appreciated.

Do you want me to commit that? Or can you with jhb@'s approval?

This revision is now accepted and ready to land.Jul 7 2026, 2:45 PM
This revision now requires review to proceed.Jul 7 2026, 5:44 PM

Do you want me to commit that? Or can you with jhb@'s approval?

Since I don't have commit bit yet, could you push it for me? Thanks:)

In D58065#1332040, @minsoochoo0122_proton.me wrote:

Since I don't have commit bit yet, could you push it for me? Thanks:)

Sure. With the minsoo.io address I presume? Also, did you do some smoke test with this change (it is low risk, but still...)? I'll probably do some tomorrow before committing.

In D58065#1332040, @minsoochoo0122_proton.me wrote:

Since I don't have commit bit yet, could you push it for me? Thanks:)

Sure. With the minsoo.io address I presume?

Yes.

Also, did you do some smoke test with this change (it is low risk, but still...)? I'll probably do some tomorrow before committing.

My computer successfully booted and I can login with this patch and the D58000, but I haven't run any test suite. I would appreciate you a lot if you can do that for me.

This revision was not accepted when it landed; it landed in state Needs Review.Jul 21 2026, 2:27 AM
This revision was automatically updated to reflect the committed changes.