From: Jakub Jelinek <jakub@redhat.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: David Luyer <david_luyer@pacific.net.au>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
"David S. Miller" <davem@redhat.com>
Subject: Re: /proc/<n>/maps growing...
Date: Mon, 6 Aug 2001 07:01:24 -0400 [thread overview]
Message-ID: <20010806070124.J3862@devserv.devel.redhat.com> (raw)
In-Reply-To: <997080081.3938.28.camel@typhaon> <20010806105904.A28792@athlon.random> <20010806063003.H3862@devserv.devel.redhat.com> <20010806124952.G15925@athlon.random>
In-Reply-To: <20010806124952.G15925@athlon.random>; from andrea@suse.de on Mon, Aug 06, 2001 at 12:49:52PM +0200
On Mon, Aug 06, 2001 at 12:49:52PM +0200, Andrea Arcangeli wrote:
> On Mon, Aug 06, 2001 at 06:30:03AM -0400, Jakub Jelinek wrote:
> > On Mon, Aug 06, 2001 at 10:59:04AM +0200, Andrea Arcangeli wrote:
> > > On Mon, Aug 06, 2001 at 04:41:21PM +1000, David Luyer wrote:
> > > > crashes for no apparent reason every 6 hours or so.. unless that could
> > > > be when
> > > > it hits some 'limit' on the number of mappings allowed?
> > >
> > > there's no limit, this is _only_ a performance issue, functionality is
> > > not compromised in any way [except possibly wasting some memory
> > > resources that could lead to running out of memory earlier].
> >
> > There is a limit, /proc/sys/vm/max_map_count.
>
> in mainline it's not a sysctl, btw.
Even worse, it means people not using -ac kernels cannot malloc a lot of
memory but by recompiling the kernel.
Jakub
next prev parent reply other threads:[~2001-08-06 11:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 6:41 /proc/<n>/maps growing David Luyer
2001-08-06 7:43 ` Chris Wedgwood
2001-08-06 8:59 ` Andrea Arcangeli
2001-08-06 9:20 ` David S. Miller
2001-08-06 9:46 ` Chris Wedgwood
2001-08-06 10:57 ` Andrea Arcangeli
2001-08-06 12:26 ` Chris Wedgwood
2001-08-06 12:36 ` Andrea Arcangeli
2001-08-06 12:45 ` Chris Wedgwood
2001-08-06 12:50 ` Andrea Arcangeli
2001-08-06 13:06 ` David S. Miller
2001-08-06 13:29 ` Andrea Arcangeli
2001-08-06 17:27 ` Linus Torvalds
2001-09-03 15:44 ` mmap-rb-7 [was Re: /proc/<n>/maps growing...] Andrea Arcangeli
2001-08-06 17:20 ` /proc/<n>/maps growing Linus Torvalds
2001-08-07 2:24 ` David Luyer
2001-08-06 17:46 ` Anton Altaparmakov
2001-08-06 16:12 ` Rik van Riel
2001-08-06 17:46 ` Linus Torvalds
2001-08-06 10:30 ` Jakub Jelinek
2001-08-06 10:49 ` Andrea Arcangeli
2001-08-06 11:01 ` Jakub Jelinek [this message]
2001-08-06 11:25 ` Andrea Arcangeli
2001-08-06 17:17 ` Linus Torvalds
2001-08-06 17:26 ` Alan Cox
2001-08-06 22:55 ` Chris Wedgwood
2001-08-06 11:16 ` Jakub Jelinek
2001-08-06 17:18 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2001-08-07 3:46 Rick Hohensee
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=20010806070124.J3862@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=andrea@suse.de \
--cc=davem@redhat.com \
--cc=david_luyer@pacific.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.