From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] bug in authdial()
Date: Thu, 19 May 2016 13:07:27 +0900 [thread overview]
Message-ID: <23B73D86-C256-47D2-8329-8C42E4FFA77E@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <CAJSxfmLXKBwqi1NuAqPvT9T8ZOqGYwxqAz0p=_u=9+PuEe5deQ@mail.gmail.com>
hello,
thanks for the information.
the lookup depends on dns cache but I also don’t think it has a problem.
I think the negotiation process is innocent.
plan9 auth negotiation is fairly simple, that needs only a single step:
C→A: ticket request
A→C: encrypted ticket
I measured the times that are required for the auth server to complete the ticket request.
they are only a few milliseconds.
dialing time from client to auth server is the problem.
> 2016/05/19 2:03、Skip Tavakkolian <skip.tavakkolian@gmail.com> のメール:
>
> i don't think it's the auth lookup:
>
> supermic% time ndb/csquery /net/cs net!luna.nyx.link!ticket
> /net/tcp/clone 115.36.102.252!567
> /net/tcp/clone 2402:6b00:4040:b600::8!567
> 0.00u 0.00s 0.34r ndb/csquery /net/cs net!luna.nyx.link!ticket
> supermic% time ndb/csquery /net/cs net!grid.nyx.link!cpu
> /net/tcp/clone 115.36.102.252!17010
> /net/tcp/clone 2402:6b00:4040:b600::9!17010
> 0.00u 0.00s 0.01r ndb/csquery /net/cs net!grid.nyx.link!cpu
> supermic%
>
> i suspect it's auth negotiations.
>
>
>
> On Wed, May 18, 2016 at 6:07 AM Charles Forsyth <charles.forsyth@gmail.com> wrote:
>
> On 18 May 2016 at 01:43, arisawa <arisawa@ar.aichi-u.ac.jp> wrote:
> - p = netmkaddr(nt->val, netroot, "ticket");
> rv = dial(p, 0, 0, 0);
> if(rv >= 0)
> break;
>
> + p = netmkaddr(nt->val, “tcp", "ticket");
> rv = dial(p, 0, 0, 0);
> if(rv >= 0)
> break;
> + p = netmkaddr(nt->val, “il", "ticket");
> + rv = dial(p, 0, 0, 0);
> + if(rv >= 0)
> + break;
>
> But that's just (eventually) moving the cs search into every application and bound to specific network types.
> Why is the cs search with "net" so slow?
prev parent reply other threads:[~2016-05-19 4:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 0:43 arisawa
2016-05-18 9:14 ` cinap_lenrek
2016-05-19 14:45 ` arisawa
2016-05-19 15:43 ` lucio
2016-05-19 15:48 ` Charles Forsyth
2016-05-20 4:58 ` arisawa
2016-05-20 22:04 ` Skip Tavakkolian
2016-05-20 22:25 ` Charles Forsyth
2016-05-21 4:46 ` arisawa
2016-05-21 17:04 ` erik quanstrom
2016-05-21 23:11 ` Lyndon Nerenberg
2016-05-21 23:16 ` erik quanstrom
2016-05-21 17:06 ` erik quanstrom
2016-05-21 3:24 ` arisawa
2016-05-23 14:27 ` arisawa
2016-05-20 22:07 ` Skip Tavakkolian
2016-05-21 2:25 ` Skip Tavakkolian
2016-05-21 7:00 ` arisawa
2016-05-21 16:51 ` erik quanstrom
2016-05-21 21:45 ` Skip Tavakkolian
2016-05-21 21:48 ` erik quanstrom
2016-05-21 22:16 ` Skip Tavakkolian
2016-05-21 21:50 ` erik quanstrom
2016-05-21 22:17 ` Skip Tavakkolian
2016-05-21 22:34 ` erik quanstrom
2016-05-21 23:03 ` Skip Tavakkolian
2016-05-21 23:31 ` erik quanstrom
2016-05-21 22:53 ` David du Colombier
2016-05-18 13:06 ` Charles Forsyth
2016-05-18 17:03 ` Skip Tavakkolian
2016-05-19 4:07 ` arisawa [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=23B73D86-C256-47D2-8329-8C42E4FFA77E@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--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).