lkml.org 
[lkml]   [2002]   [Feb]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: thread_info implementation
> Date: 	Mon, 11 Feb 2002 16:46:17 -0800 (PST)
> From: "David S. Miller" <davem@redhat.com>
>
> From: Anton Blanchard <anton@samba.org>
> Date: Tue, 12 Feb 2002 07:50:48 +1100
>
> On archs where we use a register to point to current I cant see why we
> need this thread_info junk. I'd be happy if we could put it all in the
> task struct for non intel.
>
> I am in fact very happy with the thread_info implementation
> on sparc64.
>
> I was able to blow away all of the assembler offset stuff because now
> all the stuff assembly wants to get at is in one structure and it is
> trivial to compute the offsets by hand.

I hope you don't consider this a good argument to force all the other
platforms to throw away their perfectly good low-core code. Like
Anton, I do not expect any benefits from thread_info for ia64. In
fact, if anything it's going to slow things down. And we don't need
it for task coloring either. We can do that perfectly fine with the
old setup.

Thanks,

--david
-
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.111 / U:5.720 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site