From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] other kernel bug
Date: Fri, 6 Jun 2014 13:59:32 +1000 [thread overview]
Message-ID: <CAJQxxw=B-nBOsAT+DM=3=Aa7-WPJJ-KAXvNUMsTo-a0ExJt+PQ@mail.gmail.com> (raw)
In-Reply-To: <4e7130f20258c17ecdcac434656ccc5e@felloff.net>
[-- Attachment #1: Type: text/plain, Size: 144 bytes --]
Could this solve the 'why is swap so crappy?'
On 05/06/2014 11:58 AM, <cinap_lenrek@felloff.net> wrote:
> correct.
>
> --
> cinap
>
>
[-- Attachment #2: Type: text/html, Size: 400 bytes --]
next prev parent reply other threads:[~2014-06-06 3:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 1:23 Yoann Padioleau
2014-06-05 1:56 ` cinap_lenrek
2014-06-06 3:59 ` Bruce Ellis [this message]
2014-06-06 4:15 ` cinap_lenrek
2014-06-10 1:00 ` Yoann Padioleau
2014-06-10 1:07 ` erik quanstrom
2014-06-10 1:20 ` Ethan Grammatikidis
2014-06-10 4:35 ` Kurt H Maier
2014-06-10 4:46 ` cinap_lenrek
2014-06-10 5:14 ` cinap_lenrek
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=B-nBOsAT+DM=3=Aa7-WPJJ-KAXvNUMsTo-a0ExJt+PQ@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).