From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@9fans.net
Subject: Re: [9fans] bug in authdial()
Date: Fri, 20 May 2016 15:04:01 -0700 [thread overview]
Message-ID: <a36ddeba8a8a07528c503b1401d513ea@9netics.com> (raw)
In-Reply-To: <CAOw7k5h=f+PMt94P6y60NLw-VChWqPEPcN0zXLVUmCOe5DKMNQ@mail.gmail.com>
i'm a little confused by the discussion of il + tcp on authdial
causing the delay. if ndb/cs returns multiple dial strings, dialmulti
function (/sys/src/libc/9sys/dial.c) dials them all in parallel
(rfork) and the first one that returns, wins.
btw, i found a bug in dial.c (i'll send it in another message); fixing
it didn't seem to have any effect but i believe it's a bug anyway.
i instrumented the near side of cpu; the setup (including setting up
notes forwarding) looks to be less than 2 seconds. the rest can only
be attributed to local exportfs startup and remote rc startup. here
are three runs:
supermic% time ./cpu -h grid.nyx.link -k 'dom=outside.plan9.bell-labs.com' -c pwd
dial took: 165268068 ns
negotiate auth took: 159047373 ns
factotum autenticate took: 699255914 ns
lclnoteproc time: 702945750 ns
far end setup time: 157257845 ns
/usr/fst
0.00u 0.00s 7.58r ./cpu -h grid.nyx.link -k dom=outside.plan9.bell-labs.com ...
supermic% time ./cpu -h grid.nyx.link -k 'dom=outside.plan9.bell-labs.com' -c pwd
dial took: 158312233 ns
negotiate auth took: 155598573 ns
factotum autenticate took: 681558002 ns
lclnoteproc time: 684863443 ns
far end setup time: 151972579 ns
/usr/fst
0.00u 0.01s 7.22r ./cpu -h grid.nyx.link -k dom=outside.plan9.bell-labs.com ...
supermic% time ./cpu -h grid.nyx.link -k 'dom=outside.plan9.bell-labs.com' -c pwd
dial took: 176752321 ns
negotiate auth took: 175402567 ns
factotum autenticate took: 746787405 ns
lclnoteproc time: 749881615 ns
far end setup time: 172600395 ns
/usr/fst
0.00u 0.03s 8.17r ./cpu -h grid.nyx.link -k dom=outside.plan9.bell-labs.com ...
supermic%
next prev parent reply other threads:[~2016-05-20 22:04 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 [this message]
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
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=a36ddeba8a8a07528c503b1401d513ea@9netics.com \
--to=9nut@9netics.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).