On Tue, 22 May 2007, Michael Schmitz wrote:
> > > Plus we already reserve a register for the current task - we're not all
> > > that squeezed, but can't we store the per thread data at a constant offset
> > > from the task address which we already store in a register? Are all
> > > threads separate tasks at kernel level?
> >
> > We already reserve a register for the current task in kernel space.
> > [...]
> > While TLS needs some kind of pointer in user space.
> > (Of course the kernel has to update the memory pointer at every task
> > switch).
>
> That's what I meant. Can the TLS pointer be derived from the current task
> pointer in some simple way (so we don't need to reserve some other
> register)?
The TLS data is in user space, AFAIK. The kernel doesn't need to be
aware of it at all, unless we use the memory pointer approach.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
