Ralf Baechle wrote:
>
> Memset is almost always only ever invoked with a zero argument. So the
> idea was to have something like this:
>
> extern void *__memset(void *__s, int __c, size_t __count);
> extern void *bzero(void *__s, size_t __count);
>
> static inline void *memset(void *s, int c, size_t count)
> {
> if (__builtin_constant_p(c) && c == 0) {
> bzero(s, count);
> return s;
> } else
> return __memset(s, __c, count);
> }
>
> But that was never quite implemented like this as you noticed.
Well I'm not sure we really need this. bzero() is not part of the
Linux string API, so it can only be used by MIPS specific code. And
with the current implementation of bzero(), $a1 needs to be setup to 0
anyway. That's why I simply killed it...
BTW, can memset() be an inlined function ?
>
> As for the differences in the return value, they're because of of
> clear_user and __clear_user which return the number of bytes that could
> _not_ be cleared in $a2. Memset being invoked through the normal C calling
> conventions ignores this value while it's the actual result of interest for
> __clear_user.
>
Yes I noticed this. Actually I'm wondering if we couldn't add a new
function, fill_user() like the following:
extern size_t fill_user(void __user *to, int c, size_t len);
This could be used by both memset() and clear_user():
#define memset(s,c,l) ({ (void)fill(s,c,l); s; })
#define clear_user(t,l) fill_user(t,0,l)
Therefore the definition of clear_user() could be saner.
What do you think ?
Franck
