Steve Kargl <[EMAIL PROTECTED]> writes:

> Eivind Eklund wrote:
> > (Based on suggestion from Robert Watson.)
> > 
> > I want to enable INVARIANTS by default in -current.  This result in some
> > slowdown, but it also makes it more likely that we'll find bugs quickly.
> > People that want to run -current should know enough to disable it if it is
> > in the way, anyway.
> I support your proposal.  But, have a question:  Has
> anyone actually measured the performance impact of 
> INVARIANTS?  I'm tempted to suggest that INVARIANTS
> should be the default in not only -current in 5.0
> when she's released.  Anyone interested in performance
> in 5.0 will build custom kernels, and so he can turn

sorry for the late answer.

well, I'm not at all w/ you to enable INVARIANTS in -stable.
the reason is simple. I had INVARIANTS for months (years?), but in
september, I got plenty of "TRAP FAULT 12 and calcru: monotonisation"
because of this. after disabling INVARIANTS, no problems anymore.
I've posted a message about that in -stable w/ no answer, as I
remember me. so, before to enable INVARIANTS in -stable or anywhere,
the code should be much better checked, at least around kern_resource.c.

home: mailto:[EMAIL PROTECTED] work: mailto:[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to