Re: thread_info implementation

From: David S. Miller (davem@redhat.com)
Date: Tue Feb 12 2002 - 00:32:48 EST


   From: Richard Henderson <rth@twiddle.net>
   Date: Mon, 11 Feb 2002 21:26:44 -0800
   
   On another topic, I'm considering having $8 continue to be current
   and using the two-insn stack mask to get current_thread_info and
   measuring the size difference that makes.

I might put 'current' into %g7 on sparc but currently I don't think
it's worth it myself.

BTW, your "4 issue" comments assume the cpu can do 4 non-FPU
instructions per cycle, most I am aware of cannot and I think ia64
even falls into the "cannot" category. Doesn't it?

-
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/



This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:00:46 EST