From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Inducing artificial latency
Date: Wed, 16 Jun 2010 20:10:49 -0400 [thread overview]
Message-ID: <b429b60fc80929da2fb821ab99f1cf14@kw.quanstro.net> (raw)
In-Reply-To: <20100616234310.082625B76@mail.bitblocks.com>
> You'd need some plumbing in devether to demultiplex incoming
> packets addressed to this device (assuming it has its own MAC
> address).
i don't think you would. if you're using the latency device as your
ethernet device, no muxing is required.
> Something like a tap device would allow you to simulate high
> latency link, a level-2 bridge or whatever in usercode.
this is difficult to do in user space for two reasons
1. the difficulty of getting precision timing.
2. copies into/out of the kernel.
> [BTW, is there a strong reason why devether.c is in 9/pc/ and
> not 9/port/? vlan code can be factored out from various
> ether*.c to a similar portable file (if not devether.c)]
actually, most of the code has been factored out, but one step
better than you imagine. most of the code is in ../port/netif.c
which should be a good start on any type of network interface.
what remains is code littered with system dependencies. it's
worthwhile comparing pc/devether.c with kw/devether.c
by the way, there is no vlan code, as far as i know, which
is absolutely fine by me.
> > ip is not the only protocol! that's what loopback(3) does, but without
> > the real network. it would be good to plug loopback or similar into a real
> > ethernet. it's also worth looking at loopback's implementation strategy,
>
> Or bridge(3).
not sure that is too informative.
> > which allows for µs delays. sleep is just too course-grained for my
> > testing.
> >
> > dialing up random reordering would seem to me to be a feature at
> > this level.
>
> A user level simulator will make it easy to add random drops,
> reordering, filtering, NAT, etc.
what do you mean by mac-level natting? something like
hp vc? seems way too extravagant for a simple packet muncher.
by the way, if you keep the packets in the order they should
be released from the delay queue, reordering is automatic.
i suppose the delay queue gives new meaning to the term
"storage network".
- erik
next prev parent reply other threads:[~2010-06-17 0:10 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 [this message]
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=b429b60fc80929da2fb821ab99f1cf14@kw.quanstro.net \
--to=quanstro@quanstro.net \
--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).