From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Eugene Syromyatnikov <evgsyr@gmail.com>
Cc: linux-man@vger.kernel.org, Jakub Wilk <jwilk@jwilk.net>
Subject: Re: [PATCH v2] getrlimit.2: old_getrlimit/ugetrlimit and RLIM_INFINITY discrepancies
Date: Thu, 29 Jul 2021 17:24:18 +0200 [thread overview]
Message-ID: <55097d34-7cdf-c8aa-7c4c-f62ca5012de5@gmail.com> (raw)
In-Reply-To: <20210708131054.o4sgoy7barhl3kmu@jwilk.net>
Hi Eugene,
On 7/8/21 3:10 PM, Jakub Wilk wrote:
> * Eugene Syromyatnikov <evgsyr@gmail.com>, 2021-07-08, 14:17:
>> +Original Linux implementation used signed types for limits; that was
>> changed
>> +(along with the value of the
>> +.B RLIM_INFINITY
>> +constant)
>> +.\"
>> http://repo.or.cz/davej-history.git/blobdiff/129f8758d8c41e0378ace0b6e2f56bbb8a1ec694..15305d2e69c3a838bacd78962c07077d2821f255:/include/linux/resource.h
>>
>> +during 2.4 development cycle, as it wasn't compatible
>
> Oh, interesting.
>
> That would explain why the man page incorrectly claims the upper limit
> for RLIMIT_AS is 2 GiB on 32-bit systems.
>
>> +Also worth noting that Several architectures decided not to change
>
> s/Several/several/;
> or maybe s/Also worth noting that //.
>
When you send a v2 of this, please add me to CC or TO, so that it's
easier for me to notice it.
Thanks,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
prev parent reply other threads:[~2021-07-29 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 12:17 [PATCH v2] getrlimit.2: old_getrlimit/ugetrlimit and RLIM_INFINITY discrepancies Eugene Syromyatnikov
2021-07-08 13:10 ` Jakub Wilk
2021-07-29 15:24 ` Alejandro Colomar (man-pages) [this message]
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=55097d34-7cdf-c8aa-7c4c-f62ca5012de5@gmail.com \
--to=alx.manpages@gmail.com \
--cc=evgsyr@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).