From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx and native networking
Date: Wed, 11 Feb 2009 08:42:03 -0500 [thread overview]
Message-ID: <9ab217670902110542t5bdb7657h101311ab08781d11@mail.gmail.com> (raw)
In-Reply-To: <65f44e44bfe4f7f02cdad861b35317cf@quanstro.net>
2009/2/11 erik quanstrom <quanstro@quanstro.net>:
> On Wed Feb 11 07:27:47 EST 2009, anothy@gmail.com wrote:
>> Devon got this working for him about a month and a half ago; see this message:
>> http://9fans.net/archive/2008/12/501
>> I've still not made it work for me (on OS X), but i think the issues
>> are actually in changes outside the ethernet stuff. I haven't had much
>> time to dig in.
>
> it's been working well for me. i've been using etherrs (raw socket)
> on linux. the pcap version didn't work very well for me. probablly
> due to some linux misconfiguration. also, if you're looking to ping,
> make sure that the filter compiled into etherve.c doesn't drop non-ip
> packets. arp is not ip.
I fixed that issue some time ago; it turned out that the performance
issue was something that is built into pcap to buffer packets for a
certain time period. So there was always an additional 500ms latency
on it because it was waiting that long before it returned its packet
buffer up to the OS. I believe I also have the code in hg doing the
right thing with the filter, as the pcap version did end up working
for me.
--dho
> unfortunately, what you can't do is boot from a plan 9 fs. and since
> 9vx requires many more cycles and much more memory than drawterm,
> i've fallen back to that. a faster linux machine might have lead to a
> different decision.
>
> - erik
prev parent reply other threads:[~2009-02-11 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 9:50 prem
2009-02-11 12:23 ` Anthony Sorace
2009-02-11 12:52 ` Devon H. O'Dell
2009-02-11 13:25 ` erik quanstrom
2009-02-11 13:42 ` Devon H. O'Dell [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=9ab217670902110542t5bdb7657h101311ab08781d11@mail.gmail.com \
--to=devon.odell@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).