lkml.org 
[lkml]   [2002]   [Feb]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: thread_info implementation
From
   From: David Mosberger <davidm@hpl.hp.com>
Date: Mon, 11 Feb 2002 18:46:00 -0800

OK, so back to square one: why am I supposed to do all this work for
something that will likely slow things slightly down and, at best,
doesn't hurt performance? The old set up works great and as far as
I'm concerned, is not broken.

It keeps your platform the same, and it does help other platforms.
It is the nature of any abstraction change we make in the kernel
that platforms have to deal with.

So at least we're to the point where you could be convinced that
there are no down sides to the change? Let's go over your list:

1) massive locore assembly changes

ummm no, just put current_thread_info into your thread register

2) pointer dereference causes performance problems

ummm no, not really, go test it for yourself if you don't
believe me

This only leaves "I don't want to do the conversion because it has
no benefit to ia64." Well, it doesn't hurt your platform either,
so just cope :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:24    [W:0.145 / U:0.404 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site