From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Starting rio on combined CPU, file and auth
Date: Fri, 5 May 2017 14:24:29 +0100 [thread overview]
Message-ID: <CAOw7k5hckTKHNocHcAbBbX7BG0V3LN7t8d1xaJKFi=H7u8mwvQ@mail.gmail.com> (raw)
In-Reply-To: <CAMVULc4+cBUZZHdDbN31BPjvGTm2C+f9o6BGR4PgbP4VN3eLVg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 243 bytes --]
On 5 May 2017 at 02:22, Alex Musolino <musolinoa@gmail.com> wrote:
>
> "CPU servers typically don't have any reason to run rio on a local draw
> device."
>
I don't even bother including the draw device and hangers-on in cpu servers.
[-- Attachment #2: Type: text/html, Size: 575 bytes --]
prev parent reply other threads:[~2017-05-05 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <351618734.2458204.1493931402128.ref@mail.yahoo.com>
2017-05-04 20:56 ` G B
2017-05-05 0:41 ` Alex Musolino
2017-05-05 1:00 ` Skip Tavakkolian
2017-05-05 1:22 ` Alex Musolino
2017-05-05 13:24 ` Charles Forsyth [this message]
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='CAOw7k5hckTKHNocHcAbBbX7BG0V3LN7t8d1xaJKFi=H7u8mwvQ@mail.gmail.com' \
--to=charles.forsyth@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).