From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Inducing artificial latency
Date: Tue, 15 Jun 2010 22:20:23 -0700 [thread overview]
Message-ID: <e747af819375671db4e7b5826bcdd9ff@9netics.com> (raw)
In-Reply-To: <AANLkTinvY5oRnf2dVbAXeiRAv10Ucg9VDTjO1N6CRkfT@mail.gmail.com>
any reason loopback(3) wont work? it has options for delay and latency.
> I'm going to be doing some work with 9P and high-latency links this
> summer and fall. I need to be able to test things over a high-latency
> network, but since I may be modifying the kernel, running stuff on
> e.g. mordor is not the best option. I have enough systems here to do
> the tests, I just need to artificially add latency between them.
>
> 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.
>
> I have not really done any networking stuff or filesystems work on
> Plan 9; thus far, I've confined myself to kernel work. I could be
> completely mistaken about how 9P and networking behave, so I'm asking
> for opinions and suggestions. For my part, I'm trying to find good
> example filesystems to read (I've been looking at gpsfs, for
> instance).
>
>
> John
> --
> "With MPI, familiarity breeds contempt. Contempt and nausea. Contempt,
> nausea, and fear. Contempt, nausea, fear, and .." -- Ron Minnich
prev parent reply other threads:[~2010-06-16 5:20 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
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 [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=e747af819375671db4e7b5826bcdd9ff@9netics.com \
--to=9nut@9netics.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).