From: grg22@ai.mit.edu
To: Linux-MM@kvack.org, dca@torrent.com, grg22@ai.mit.edu
Subject: Re: getrusage
Date: Fri, 6 Aug 1999 22:00:00 -0400 [thread overview]
Message-ID: <199908070200.WAA03531@skydive.ai.mit.edu> (raw)
On Tue, Aug 03, 1999 at 04:02:53PM +0200, dca@torrent.com wrote:
>
> Here are the relevant entries from struct rusage:
>
> long ru_maxrss; /* maximum resident set size */
> long ru_ixrss; /* integral shared memory size */
> long ru_idrss; /* integral unshared data size */
> long ru_isrss; /* integral unshared stack size */
If you do fix this, could you please make all these entries *unsigned*
longs? We need to convert over to using the full 32 bits to allow for full
usage of the memory. I believe negative values are disallowed for any of
these resource limits and usages, so this particular change shouldn't break
anything anywhere.
Currently linux tries to allow 3GB of virtual, but we're stuck at 2GB
because the resource limits are signed longs rather than unsigned.
There are several patches submitted to fix this. Basically all the
longs in include/linux/resource.h should be unsigned; IMHO the definition
of INFINITY there should be ~0UL (the current definition, ~0UL>>1, is what
enforces the limit of max 2GB), but I think some differ in opinion here.
We should also get the libc people to correct the get/setrlimit and
getrusage library calls to support unsigned longs. (What's the mailing
list for glibc? I can't seem to locate one specifically for it.)
thanks,
grg.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next reply other threads:[~1999-08-07 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-07 2:00 grg22 [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-08-08 18:02 getrusage dca
1999-08-03 14:02 getrusage dca
1999-08-03 14:21 ` getrusage Andi Kleen
1999-08-02 21:59 getrusage dca
1999-08-03 11:04 ` getrusage Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199908070200.WAA03531@skydive.ai.mit.edu \
--to=grg22@ai.mit.edu \
--cc=Linux-MM@kvack.org \
--cc=dca@torrent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox