9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@labs.coraid.com>
To: nemo@lsub.org, 9fans@9fans.net, quanstro@labs.coraid.com
Subject: Re: [9fans] gar nix!
Date: Fri, 16 Sep 2011 11:33:23 -0400	[thread overview]
Message-ID: <9f50baed53970831578c08bdb2156eaa@coraid.com> (raw)
In-Reply-To: <CA+N-5bbt92zqNpt0KW4prykyTxjYNHJJ7LuUCj4n3EACyC5GvQ@mail.gmail.c>

On Fri Sep 16 11:31:58 EDT 2011, nemo@lsub.org wrote:
> I agree, but I think it's ok if we use them only if we have them, and rely on
> just 2M otherwise.
>
> On Fri, Sep 16, 2011 at 5:28 PM, ron minnich <rminnich@gmail.com> wrote:
> > On Fri, Sep 16, 2011 at 7:57 AM, erik quanstrom
> > <quanstro@labs.coraid.com> wrote:
> >
> >> please don't make it required.  there's already array of page sizes per mach.
> >
> > sorry, but time moves forward. We need the 1G pages for user mode
> > anyway -- so the fact that you can run on older machines is a happy
> > coincidence but it will die the first time you run a process that uses
> > more than 1G. Reducing PTE count by 512 is a not insignificant cost. I
> > expect to put the 1G pages for the kernel map back in in the next
> > while.

i would hate to have dogmatic rules like this limit cooperation.  i'm really
excited about nix.  please don't kill the buzz off so quickly.

- erik



  parent reply	other threads:[~2011-09-16 15:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16  1:19 erik quanstrom
2011-09-16  5:44 ` Noah Evans
2011-09-17 19:41   ` erik quanstrom
2011-09-17 20:03     ` Noah Evans
2011-09-16  5:56 ` ron minnich
     [not found] ` <CAP6exYLuD6ZeOwCfY9TcgSWEYp-2QH-7qUO713GL0cravJ2FzA@mail.gmail.c>
2011-09-16  6:46   ` erik quanstrom
2011-09-16  7:02     ` Nemo
2011-09-16  7:52     ` dexen deVries
2011-09-16 13:36     ` Charles Forsyth
2011-09-16 14:39     ` ron minnich
     [not found]     ` <CAP6exYLy6sicg42A+7D=bmpWtv=p_an3c5=OQw9YB2oxPXhR2A@mail.gmail.c>
2011-09-16 14:57       ` erik quanstrom
2011-09-16 15:28         ` ron minnich
2011-09-16 15:31           ` Francisco J Ballesteros
     [not found]           ` <CA+N-5bbt92zqNpt0KW4prykyTxjYNHJJ7LuUCj4n3EACyC5GvQ@mail.gmail.c>
2011-09-16 15:33             ` erik quanstrom [this message]
2011-09-16 15:36               ` Francisco J Ballesteros
2011-09-16 15:44                 ` ron minnich
2011-09-16 16:07                   ` Francisco J Ballesteros
     [not found]               ` <CA+N-5bYJ1VBpqQENUy5fZirE_Joa9E6RE8rJbvaFwh065zd2TA@mail.gmail.c>
2011-09-16 15:37                 ` erik quanstrom
2011-09-16 18:24     ` ron minnich
2011-09-16 22:23       ` Charles Forsyth
2011-09-16 22:27         ` erik quanstrom
2011-09-17  3:39           ` Bruce Ellis
2011-09-17  7:35             ` Charles Forsyth
2011-09-17  7:44           ` Charles Forsyth
2011-09-17  8:45             ` Charles Forsyth
     [not found]     ` <CAP6exYK+aoYcaC+LLo4XdPmZ1jvPQ0dAgZuUkmX7_xZQ+h3+gQ@mail.gmail.c>
2011-09-16 18:32       ` erik quanstrom
2011-09-16 18:44         ` Francisco J Ballesteros

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=9f50baed53970831578c08bdb2156eaa@coraid.com \
    --to=quanstro@labs.coraid.com \
    --cc=9fans@9fans.net \
    --cc=nemo@lsub.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).