From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] snoopy oddity
Date: Mon, 22 Jan 2007 16:28:26 -0500 [thread overview]
Message-ID: <ee9e417a0701221328k74e65b5r5f040e67cf962@mail.gmail.com> (raw)
In-Reply-To: <8803e7b955b023baa49ec12012579323@coraid.com>
> so i would assume that this isn't going to work very well for
> high bandwidth, scaled tcp connections?
like i said before, it all depends on how fast you can run snoopy.
if you are maxing out the machine doing tcp, there is not going
to be much left for snoopy. other ways to avoid losing packets
include running snoopy redirected into a file (don't get stuck waiting
for the window system to scroll the window) or running with the -d
flag (avoid the overhead of formatting the packets for display).
russ
next prev parent reply other threads:[~2007-01-22 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 16:23 erik quanstrom
2007-01-22 16:54 ` Russ Cox
2007-01-22 18:34 ` erik quanstrom
2007-01-22 21:28 ` Russ Cox [this message]
2007-01-22 22:06 ` erik quanstrom
2007-01-23 18:14 ` ron minnich
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=ee9e417a0701221328k74e65b5r5f040e67cf962@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).