From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Inducing artificial latency
Date: Tue, 15 Jun 2010 14:53:06 -0700 [thread overview]
Message-ID: <AANLkTinTzHofOgR-Gqa8wiiwJvHLOow98BgpPHsZy1Qc@mail.gmail.com> (raw)
In-Reply-To: <7390b81f52bc8af2a1925fa45b039597@kw.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
On Tue, Jun 15, 2010 at 2:39 PM, erik quanstrom <quanstro@quanstro.net>wrote:
> > I've come up with a basic idea, but before I go diving in I want to
> > run it by 9fans and get opinions. What I'm thinking is writing a
> > synthetic file system that will collect writes to /net; to simulate a
> > high-latency file copy, you would run this synthetic fs, then do "9fs
> > remote; cp /n/remote/somefile .". If it's a control message, that gets
> > sent to the file immediately, but if it's a data write, that data
> > actually gets held in a queue until some amount of time (say 50ms) has
> > passed, to simulate network lag. After that time is up, the fs writes
> > to the underlying file, the data goes out, etc.
>
> instead, why don't you create a simulated ethernet device
> that adds in a delay before sending the packet along to a
> real ethernet device.
>
> the only trick will be getting the simulated ethernet to
> grab the real ethernet during setup. i imagine that you'll
> need something like
> ether0=type=fake
> fake=real=#l1/ether1 i=10 iσ=20 o=5 oσ=0
> in plan9.ini
>
> - erik
>
> Could one write a filesystem server that is a passthrough to the ethernet
device instead, adding latency? Or is this really going to need to be a new
device?
[-- Attachment #2: Type: text/html, Size: 1713 bytes --]
next prev parent reply other threads:[~2010-06-15 21:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 21:29 John Floren
2010-06-15 21:39 ` Jorden M
2010-06-15 22:06 ` Enrique Soriano
2010-06-15 21:39 ` erik quanstrom
2010-06-15 21:53 ` David Leimbach [this message]
2010-06-15 21:59 ` erik quanstrom
2010-06-15 21:45 ` Devon H. O'Dell
2010-06-15 22:43 ` John Floren
2010-06-15 23:01 ` Devon H. O'Dell
2010-06-16 19:04 ` John Floren
2010-06-16 22:15 ` Francisco J Ballesteros
2010-06-16 22:31 ` erik quanstrom
2010-06-16 22:58 ` EBo
2010-06-16 23:43 ` Bakul Shah
2010-06-17 0:10 ` erik quanstrom
2010-06-17 2:02 ` Bakul Shah
2010-06-17 3:32 ` erik quanstrom
2010-06-15 21:58 ` Gorka Guardiola
2010-06-15 22:07 ` erik quanstrom
2010-06-15 22:14 ` Gorka Guardiola
2010-06-22 14:53 ` John Floren
2010-06-22 15:03 ` John Floren
2010-06-16 5:20 ` Skip Tavakkolian
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=AANLkTinTzHofOgR-Gqa8wiiwJvHLOow98BgpPHsZy1Qc@mail.gmail.com \
--to=leimy2k@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).