On Fri, 1 Sep 2000, Pavel Machek wrote:
> > > > On Thu, 31 Aug 2000, Petko Manolov wrote:
> > > >
> > > > [Snipped...]
> > > >
> > > > Good. You understand. Keep up the good work.
> > >
> > >
> > > I realy would like to see this code in use ;-)
> > After you test it **THOUROUGHLY**, send a patch to Linus. I
> > recommend testing it in a user-mode program with all kinds of
> > sizes/shapes/lengths/offsets, etc., and making certain that you
> > don't destroy any registers that are "precious" for the
> > usual versions of gcc.
> > If your patch doesn't hurt anything, even if it only adds marginal
> > performance, I'm pretty sure that Linus will accept it.
> I think patch like this is not safe for 2.4.X-pre.
Not safe only in that there is sooooo much stuff changed all at once
that it'd be a good idea not to change anything that doesn't have to
be changed. I agree.
> However, in 2.5.0 we should apply it, and force it on *all* cpus just
> to test it well. Then in 2.5.10 we should turn it off for
Once 2.4 is released, has its usual bug-fixes, becomes reliable, then
Petko can send his diff. That way, new problems won't be thought to
be a result of his patch. That us a good idea.
Penguin : Linux version 2.2.15 on an i686 machine (797.90 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Sep 07 2000 - 21:00:12 EST