[DragonFlyBSD - Bug #2431] (Closed) dfly usched on UP kernel crash on boot

[Thomas Nikolajsen via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #2431 has been updated by Thomas Nikolajsen.

Status changed from New to Closed

Resolved by commit 40d9cbc812e431e3fc980040a50b09ca82c2ce1a
----------------------------------------
Bug #2431: dfly usched on UP kernel crash on boot
http://bugs.dragonflybsd.org/issues/2431

Author: Thomas Nikolajsen
Status: Closed
Priority: Normal
Assignee: 
Category: 
Target version: 


On master using UP kernel our default usched (dfly) crash on boot.

Using bsd4 usched works (kern.user_scheduler="bsd4").

UP kernel doesn't build, as WERROR triggers on some unused var, this is trivially fixed.

Should we fix dfly usched or just declare it SMP only (and bsd4 as default on UP)?

I guess UP system will have no benefit from dfly, vs bsd4.

(another router, which have been mentioned on irc is removing UP kernel support;
this needs SMP kernel support on all systems, and no noticiable performance diff IMO)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account