lkml.org 
[lkml]   [2007]   [Jul]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch 0/6] sys_indirect RFC - sys_indirect introduction
On 7/2/07, Davide Libenzi <davidel@xmailserver.org> wrote:
> Never be usable? I made you a concrete example that is like 8 months old.
> And *that* could not have been cleanly handled with the flat structure
> idea.

First of all, sigmasks are not widely needed. Second, why on earth
shouldn't it be possible with a flat structure? Just have the sigmask
in the same position. It's no magic.


> But there are
> examples (and the signal stuff is one of them), where you do need the
> set_context+syscall+unset_context abstraction, for all cases where the
> kernel already has its own internal data strctures. In those cases you'd
> have to spread sys_internal context knowledge all around the kernel,
> whereas the current solution allows you to confine the code inside
> kernel/indirect.c

Nonsense. Whether you have a new word in the task structure or a
pointer to a structure, you have to embed knowledge of this
indirection in every affected code paths. There is no difference
here. The only difference is that trying to force everything through
an artificially complicated common entry code.

I hope that Andrew+Linus will see through this. I'm done arguing.
-
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: 2007-07-03 02:33    [from the cache]
©2003-2011 Jasper Spaans