From: "Antonin Vecera" <antonin.vecera@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] patch/create problem (error?)
Date: Fri, 12 Sep 2008 19:28:02 +0200 [thread overview]
Message-ID: <10b109140809121028k477d0881ve3d2c860b85c9d69@mail.gmail.com> (raw)
In-Reply-To: <a78c80811d831cabebc5cb1bdbce77c9@quanstro.net>
On Fri, Sep 12, 2008 at 1:47 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>>>> I had problem to create a patch - the command didn't finish for long long time.
>>>
>>> I created a patch yesterday and it worked fine. It is fairly slow as it
>>> diff's all the files you have changed with those on sources.
>>>
>>> Sadly the 9p protocol is quite badly effected by high (intercontinential) RTTs.
>>>
>>> -Steve
>>
>> There were only 2 files in the patch. I wait for about 10 minutes and nothing.
>> But then I tried to copy a file from command line.
>> If I copied an ordinary file (to /n/sources) it was done immediately.
>> But If I copied a file from bind-ed(!) directory it was endless...
>> There was no diff, only copy file.
>
> i would guess the problem is a bit different. i'm assuming that
> reads from sources work fine. it's not until you try to write there
> that there's a problem.
>
> this sounds like a mtu problem. i have a similar problem.
> i am not able to submit patches over one particular
> network interface. however, if i use a lower mtu, things work fine.
> i believe this is because the dumpy dsl modem we have
> blocks icmp messages.
>
> you could lower the mtu on the interface, but rather than
> punishing all traffic, i wrote a program called cpmtu. cpmtu
> is attached. if you define this function
> fn cp {cpmtu -m 700 $*}
> before you run patch/create, i believe patch should work
> properly for you.
>
> as an aside: i don't think 9p itself limits plan 9 performance
> over high-latency links. the limitations have more to do with
> the number of outstanding messages, which is 1 in the mnt
> driver.
>
> - erik
>
It seems you are right. I think I used in my previous tests too
specific (small) files.
I will try to play with mtu and with your "cpmtu".
Anyway, does 9P and Plan9 know about "path MTU discovery"?
Or have I something wrong at my firewall/router?
Other of my computers (FreeBSD,Windows) don't have such problems.
Antonin
next prev parent reply other threads:[~2008-09-12 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 7:34 Antonin Vecera
2008-09-12 7:54 ` Steve Simon
2008-09-12 8:34 ` Antonin Vecera
2008-09-12 11:47 ` erik quanstrom
2008-09-12 17:28 ` Antonin Vecera [this message]
2008-09-12 18:16 ` erik quanstrom
2008-09-13 19:14 ` Antonin Vecera
2008-09-14 1:11 ` Dave Eckhardt
2008-09-14 1:45 ` erik quanstrom
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=10b109140809121028k477d0881ve3d2c860b85c9d69@mail.gmail.com \
--to=antonin.vecera@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).