Re: [patch 0/6] sys_indirect RFC - sys_indirect introduction
- From: "Ulrich Drepper" <drepper@xxxxxxxxx>
- Date: Sat, 30 Jun 2007 14:54:06 -0700
On 6/30/07, Davide Libenzi <davidel@xxxxxxxxxxxxxxx> wrote:
But, a __get_user(), once you scrap off all the gcc wrapping, is bacially
a move. That could even be removed, but really I don't see the reason
since it allows for a cleaner strcture definition in userland.
Don't generalize. The 4G/4G kernel, for instance, doesn't have this
property. Who knows what else will come up. Anyway, two memcpy are
slower than one.
But this does not allow more than one context to be set at a time, like
the current implementation does. Ie, the current implementation allow you
to:
Of course it does. It just requires an appropriate union element.
I've listed flags and sigset_t as separate union elements since I
cannot think of a place where we need both extensions. Should there
be one this can easily be changed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [patch 0/6] sys_indirect RFC - sys_indirect introduction
- From: Davide Libenzi
- Re: [patch 0/6] sys_indirect RFC - sys_indirect introduction
- From: Ulrich Drepper
- Re: [patch 0/6] sys_indirect RFC - sys_indirect introduction
- From: Davide Libenzi
- [patch 0/6] sys_indirect RFC - sys_indirect introduction
- Prev by Date: Re: A simpler variant on sys_indirect?
- Next by Date: Re: [PATCH] b44: power down PHY when interface down
- Previous by thread: Re: [patch 0/6] sys_indirect RFC - sys_indirect introduction
- Next by thread: [patch 1/6] sys_indirect RFC - fast sequential allocator
- Index(es):