From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] πp
Date: Fri, 15 Oct 2010 18:05:25 -0400 [thread overview]
Message-ID: <AANLkTikvyMinoZHqTP40HZZcvCHC0xnkxwK6yb1LGTio@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1010152341130.2220@sampi>
It is probably worth trying. However, it wouldn't make copying a file
from sources any faster, or help a Blue Gene node do a snapshot any
quicker.
John
2010/10/15 Julius Schmidt <aiju@phicode.de>:
> Perhaps I'm getting this all wrong, but to me this seems like an
> interesting idea, especially if you consider the impact of being "near
> the files" on some classically considered computationally stressy tasks
> like compiling (esp. with kencc). So moving the code near the data
> definitely seems worth trying.
>
> aiju
>
>
> On Fri, 15 Oct 2010, Latchesar Ionkov wrote:
>
>> There are definitely cases when moving the code instead of the data
>> makes sense. But that discussion is mostly unrelated to the one on how
>> to make the file I/O work better over high-latency links.
>>
>> 2010/10/15 erik quanstrom <quanstro@quanstro.net>:
>>>
>>> On Fri Oct 15 12:33:19 EDT 2010, lucho@ionkov.net wrote:
>>>>
>>>> What if the data your process needs is located on more than one
>>>> server? Play ping-pong?
>>>
>>> one either plays ping pong with the process or data. one
>>> could imagine cases where the former case makes sense.
>>>
>>> - erik
>>>
>>>
>>
>
next prev parent reply other threads:[~2010-10-15 22:05 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 19:46 Eric Van Hensbergen
2010-10-13 22:13 ` David Leimbach
2010-10-13 22:36 ` roger peppe
2010-10-13 23:15 ` David Leimbach
2010-10-14 4:25 ` blstuart
2010-10-13 23:24 ` Venkatesh Srinivas
2010-10-14 21:12 ` Latchesar Ionkov
2010-10-14 21:48 ` erik quanstrom
2010-10-14 22:14 ` dorin bumbu
2010-10-15 14:07 ` erik quanstrom
2010-10-15 14:45 ` Russ Cox
2010-10-15 15:41 ` Latchesar Ionkov
2010-10-15 21:13 ` dorin bumbu
2010-10-15 22:13 ` erik quanstrom
2010-10-15 23:30 ` dorin bumbu
2010-10-15 23:45 ` cinap_lenrek
2010-10-15 23:54 ` dorin bumbu
2010-10-15 7:24 ` Sape Mullender
2010-10-15 10:41 ` hiro
2010-10-15 12:11 ` Jacob Todd
2010-10-15 13:06 ` Iruatã Souza
2010-10-15 13:23 ` Sape Mullender
2010-10-15 14:57 ` David Leimbach
2010-10-15 14:54 ` David Leimbach
2010-10-15 14:59 ` Francisco J Ballesteros
2010-10-15 16:19 ` cinap_lenrek
2010-10-15 16:28 ` Lyndon Nerenberg
2010-10-15 17:54 ` Nemo
2010-10-15 17:49 ` ron minnich
2010-10-15 18:56 ` erik quanstrom
2010-10-15 16:31 ` Latchesar Ionkov
2010-10-15 16:40 ` cinap_lenrek
2010-10-15 16:43 ` Latchesar Ionkov
2010-10-15 17:11 ` cinap_lenrek
2010-10-15 17:15 ` Latchesar Ionkov
2010-10-15 19:10 ` erik quanstrom
2010-10-15 19:16 ` Latchesar Ionkov
2010-10-15 21:43 ` Julius Schmidt
2010-10-15 22:02 ` David Leimbach
2010-10-15 22:05 ` John Floren [this message]
2010-10-15 16:45 ` ron minnich
2010-10-15 17:26 ` Eric Van Hensbergen
2010-10-15 17:45 ` Charles Forsyth
2010-10-15 17:45 ` ron minnich
2010-10-15 18:03 ` Bakul Shah
2010-10-15 18:45 ` David Leimbach
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=AANLkTikvyMinoZHqTP40HZZcvCHC0xnkxwK6yb1LGTio@mail.gmail.com \
--to=slawmaster@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).