From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan 9 overcommits memory?
Date: Sun, 2 Sep 2007 22:11:23 -0400 [thread overview]
Message-ID: <2ba7208249d3f9061b3d4638afea4fd5@quanstro.net> (raw)
In-Reply-To: <13426df10709021847o1df19364j2d22a87d425c6505@mail.gmail.com>
> but most people can live with the overcommit, as witness the fact that
> most of us do and never know it.
>
> If you can't live with overcommit, maybe you need a wrapper that:
> sets up to catch the note (I am assuming here that you get one; do you?)
> malloc
> zero memory you malloc'ed (which will get the pages in)
> die reasonably if you get the note
but why introduce unpredictability? who really programs as if
memory is not overcommited? i would bet that acme and most
residents of /sys/src/cmd could do quite bad things to you in these
cases. there's no waserror() in userland to wrap around memset.
how much memory can be wasted by assuming that all brk'ed memory
can be used?
- erik
next prev parent reply other threads:[~2007-09-03 2:11 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 11:41 erik quanstrom
2007-09-02 21:27 ` Russ Cox
2007-09-03 0:43 ` erik quanstrom
2007-09-04 8:47 ` Douglas A. Gwyn
2007-09-04 13:39 ` David Leimbach
2007-09-04 14:41 ` erik quanstrom
2007-09-04 15:54 ` David Leimbach
2007-09-04 17:37 ` sqweek
2007-09-04 18:10 ` ron minnich
2007-09-04 18:53 ` sqweek
2007-09-03 1:23 ` Scott Schwartz
2007-09-03 1:47 ` ron minnich
2007-09-03 2:11 ` erik quanstrom [this message]
2007-09-03 2:11 ` erik quanstrom
2007-09-04 8:48 ` Douglas A. Gwyn
2007-09-03 5:28 ` Scott Schwartz
2007-09-03 3:38 geoff
2007-09-03 5:35 ` Scott Schwartz
2007-09-03 6:05 ` Uriel
2007-09-03 13:33 ` erik quanstrom
2007-09-03 17:09 ` john
2007-09-03 17:17 ` Gorka Guardiola
2007-09-03 17:25 ` Francisco J Ballesteros
2007-09-03 17:30 ` john
2007-09-03 19:47 ` Charles Forsyth
2007-09-03 19:46 ` Uriel
2007-09-03 19:54 ` Charles Forsyth
2007-09-03 19:54 ` Uriel
2007-09-03 20:34 ` geoff
2007-09-03 20:16 ` erik quanstrom
2007-09-03 17:32 ` erik quanstrom
2007-09-03 17:39 ` Francisco J Ballesteros
2007-09-03 17:43 ` john
2007-09-03 17:45 ` john
2007-09-03 19:52 ` Charles Forsyth
2007-09-05 8:33 ` sqweek
2007-09-04 8:48 ` Douglas A. Gwyn
2007-09-03 18:13 ` geoff
2007-09-03 20:17 ` erik quanstrom
2007-09-03 20:48 ` geoff
2007-09-03 22:01 ` erik quanstrom
2007-09-03 22:43 ` Charles Forsyth
2007-09-03 23:51 ` erik quanstrom
2007-09-04 0:04 ` Charles Forsyth
2007-09-04 14:44 ` erik quanstrom
2007-09-04 15:07 ` Charles Forsyth
2007-09-04 15:18 ` ron minnich
2007-09-04 15:18 ` Charles Forsyth
2007-09-05 8:48 ` Douglas A. Gwyn
2007-09-05 10:53 ` erik quanstrom
2007-09-06 8:42 ` Douglas A. Gwyn
2007-09-06 17:15 ` Joel C. Salomon
2007-09-06 19:38 ` ron minnich
2007-09-06 20:18 ` Charles Forsyth
2007-09-06 23:37 ` Steve Simon
2007-09-07 3:09 ` Roman Shaposhnik
2007-09-07 4:09 ` Bruce Ellis
2007-09-07 4:25 ` Lyndon Nerenberg
2007-09-07 4:37 ` Bruce Ellis
2007-09-07 4:43 ` Lyndon Nerenberg
2007-09-10 15:24 ` roger peppe
2007-09-07 10:55 ` erik quanstrom
2007-09-04 23:32 ` erik quanstrom
2007-09-03 21:16 ` Charles Forsyth
2007-09-03 21:19 ` ron minnich
2007-09-03 21:41 ` Eric Van Hensbergen
2007-09-03 21:51 ` erik quanstrom
2007-09-03 13:21 ` erik quanstrom
2007-09-03 14:01 ` Sape Mullender
2007-09-03 14:32 ` erik quanstrom
2007-09-03 15:28 ` Sape Mullender
2007-09-04 4:32 ` lucio
2007-09-04 7:23 ` Dave Eckhardt
2007-09-04 8:48 ` Douglas A. Gwyn
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=2ba7208249d3f9061b3d4638afea4fd5@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/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).