Re: RLIM_INFINITY and 2.3.32

Jakub Jelinek (jakub@redhat.com)
Tue, 14 Dec 1999 23:47:47 +0100

> On Alpha, there are no problems, since RLIM_INFINITY is changed
> back to the old value.
>
> On Intel, we have a new ugetrlimit syscall, so there are no
> problems, too.
>
> But what is with the other architectures like m68k, ppc, sparc,
> sparc64 and others ? There the parameter for the syscall has
> changed (unsinged long vs. long), but we don't have a new syscall.

On sparc64, I think we'll use 0xffffffffffffffff and we don't need any
old_getrlimit syscall simply because I can recompile all my 64bit userland
and I doubt anyone else has it.

On sparc32, I'd prefer to go back to 0x7fffffff but haven't heard Davem's
opinion on this.

If it will end up like this, glibc headers shall look like:
#if __WORDSIZE == 64
#define RLIM_INFINITY 0xffffffffffffffff
#else
#define RLIM_INFINITY 0x7fffffff
#endif

Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jakub@redhat.com | http://sunsite.mff.cuni.cz/~jj
Linux version 2.3.26 on a sparc64 machine (1343.49 BogoMips)
___________________________________________________________________

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/