From: Andrea Arcangeli <andrea@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: thockin@sun.com, linux-kernel@vger.kernel.org
Subject: Re: RFC: poll change
Date: Wed, 15 Aug 2001 16:13:18 +0200 [thread overview]
Message-ID: <20010815161318.C7382@athlon.random> (raw)
In-Reply-To: <20010814.163804.66057702.davem@redhat.com> <3B79BA07.B57634FD@sun.com> <20010815021110.F4304@athlon.random> <20010814.171609.75760869.davem@redhat.com>
In-Reply-To: <20010814.171609.75760869.davem@redhat.com>; from davem@redhat.com on Tue, Aug 14, 2001 at 05:16:09PM -0700
On Tue, Aug 14, 2001 at 05:16:09PM -0700, David S. Miller wrote:
> From: Andrea Arcangeli <andrea@suse.de>
> Date: Wed, 15 Aug 2001 02:11:10 +0200
>
> On Tue, Aug 14, 2001 at 04:53:43PM -0700, Tim Hockin wrote:
> > - if (nfds > NR_OPEN)
> > + if (nfds > current->rlim[RLIMIT_NOFILE].rlim_cur)
>
> Here SuS speaks about OPEN_MAX, not sure if OPEN_MAX corresponds to the
> current ulimit or to the absolute maximum (to me it sounds more like our
> NR_OPEN).
>
> Right, and our equivalent is "NR_OPEN".
I was backporting the new version to 2.2 and I noticed that by using
NR_OPEN an luser will actually be able to lock into RAM something of the
order of the dozen mbytes per process. So I'm wondering that it would be
saner to use the rlimit instead, after all I don't see much of a value
to use NR_OPEN instead of the rlimit (even if strictly speaking SuS asks
us to use NR_OPEN). Any weird program (if any) that would depend on
NR_OPEN instead of the rlimit can be easily fixed with a one liner at
most. So I guess I'd be more happy with the rlimit instead of NR_OPEN.
Comments?
Andrea
next prev parent reply other threads:[~2001-08-15 14:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B79B381.58266C13@sun.com>
[not found] ` <20010814.162710.131914269.davem@redhat.com>
[not found] ` <3B79B5F3.C816CBED@sun.com>
[not found] ` <20010814.163804.66057702.davem@redhat.com>
2001-08-14 23:53 ` RFC: poll change Tim Hockin
2001-08-14 23:53 ` David S. Miller
2001-08-15 0:08 ` Andrea Arcangeli
2001-08-15 0:09 ` Tim Hockin
2001-08-15 0:06 ` David S. Miller
2001-08-15 0:11 ` Andrea Arcangeli
2001-08-15 0:16 ` David S. Miller
2001-08-15 0:30 ` Andrea Arcangeli
2001-08-15 0:34 ` [PATCH] agreed upon " Tim Hockin
2001-08-15 0:32 ` David S. Miller
2001-08-15 14:13 ` Andrea Arcangeli [this message]
2001-08-15 14:24 ` RFC: " David S. Miller
2001-08-15 14:32 ` Andrea Arcangeli
2001-08-15 16:30 ` Hugh Dickins
2001-08-15 16:40 ` Andrea Arcangeli
2001-08-14 21:08 Tim Hockin
2001-08-14 21:43 ` David S. Miller
2001-08-14 22:38 ` Herbert Xu
2001-08-14 22:42 ` David S. Miller
2001-08-15 0:03 ` Andrea Arcangeli
2001-08-15 0:06 ` David S. Miller
2001-08-15 0:16 ` Andrea Arcangeli
2001-08-15 0:23 ` David S. Miller
2001-08-15 10:40 ` David Schwartz
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=20010815161318.C7382@athlon.random \
--to=andrea@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@sun.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