9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] gar nix!
Date: Sat, 17 Sep 2011 13:39:11 +1000	[thread overview]
Message-ID: <CAJQxxw=tqoFB-Y9PXUNdd5Zvzijo-jPAYeb+jaGk_N74tivM-w@mail.gmail.com> (raw)
In-Reply-To: <ec691076480cdecc2dd2525c0bdbc022@coraid.com>

i like the idea of dma asynchronously cleared pages for a free list.
very much a "if you take last beer stock the fridge" laziness.

brucee

On 17 September 2011 08:27, erik quanstrom <quanstro@labs.coraid.com> wrote:
> On Fri Sep 16 18:18:25 EDT 2011, forsyth@terzarima.net wrote:
>> > (can't one just preemptively map the whole text on first-fault?)
>>
>> that doesn't make sense on many architectures.
>> if there isn't a page table system, for instance, but a set of moderate size of software-managed tlbs,
>> perhaps with hardware assistance, that won't work terribly well.
>> the faults tell you what you're using right now. you need a page size, however,
>> that's appropriate for your system (including your application set), or
>> faulting lots of tiny chunks of text that your processor can execute quickly
>> will give excessive overhead.
>
> sure but we are talking about x86_64, which has a limited number of
> possible page sizes and hardware managed tlbs.
>
> it would seem that one could give the architecture code the info and
> let it decide?
>
> - erik
>
>



--
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)



  reply	other threads:[~2011-09-17  3:39 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
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 [this message]
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='CAJQxxw=tqoFB-Y9PXUNdd5Zvzijo-jPAYeb+jaGk_N74tivM-w@mail.gmail.com' \
    --to=bruce.ellis@gmail.com \
    --cc=9fans@9fans.net \
    /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).