9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] mk time-check/slice issue
Date: Wed, 18 Dec 2013 17:16:58 -0500	[thread overview]
Message-ID: <3e1e9e6fbfa856a01013a2f51b8d244f@coraid.com> (raw)
In-Reply-To: <CABwHSOv=p17DeO_VHfY1DuX4H_h18eZ2qbVmCHyZrpd5NE6CVA@mail.gmail.com>

> I think this is caused because the time slice is too short and the system
> can't tell the build times apart.  Even though main clearly came after main.8
> the system sees them as the same time.  Of course this can cause mk to
> dothe link again unnecessarily if
> mk is called again.  This is what is happening to me.  Each time I mk it
> builds less.
>
> Perhaps this is a problem with 9port under VMware.  Perhaps, in certain
> environments, the time slices are too big.
>
> Any experience or thoughts on the matter are greatly appreciated.

you are correct.  this is all about time resolution.  plan 9
times are recorded in 1s resolution, and unless you have a very slow
processor, or a very big program, building & linking a program can take
less than 1s.

- erik



  parent reply	other threads:[~2013-12-18 22:16 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 22:01 Blake McBride
2013-12-18 22:08 ` Matthew Veety
2013-12-18 22:42   ` Blake McBride
2013-12-18 22:16 ` erik quanstrom [this message]
2013-12-18 22:46   ` Blake McBride
2013-12-19  5:40     ` erik quanstrom
2013-12-19  6:07       ` Bakul Shah
2013-12-19 10:59         ` Charles Forsyth
2013-12-19 14:21           ` Oleksandr Iakovliev
2013-12-19 14:58             ` erik quanstrom
2013-12-19 14:52       ` Blake McBride
2013-12-19 14:55         ` erik quanstrom
2013-12-19 15:58           ` Blake McBride
2013-12-19 16:30             ` Tristan
2013-12-19 16:37               ` Blake McBride
2013-12-19 16:40                 ` Jacob Todd
2013-12-19 17:05                   ` Blake McBride
2013-12-19 17:24                 ` Tristan
2013-12-19 18:30                   ` Blake McBride
2013-12-19 17:59             ` Steffen Daode Nurpmeso
2013-12-19 17:07         ` a
2013-12-19 18:40           ` Blake McBride
2013-12-19 18:58             ` Kurt H Maier
2013-12-19 19:06             ` Matthew Veety
2013-12-19 19:07             ` Kurt H Maier
2013-12-19 19:20               ` Blake McBride
2013-12-19 19:27                 ` Kurt H Maier
2013-12-19 19:42                   ` Blake McBride
2013-12-19 20:02                     ` Kurt H Maier
2013-12-19 20:18                       ` erik quanstrom
2013-12-19 20:23                         ` Kurt H Maier
2013-12-19 19:35                 ` a
2013-12-19 19:09             ` a
2013-12-27 10:16               ` dexen deVries
2013-12-19 19:09             ` erik quanstrom
2013-12-19 19:29               ` Blake McBride
2013-12-19 19:39                 ` Gabriel Diaz
2013-12-19 20:15                 ` Richard Miller
2013-12-19 20:28                   ` Blake McBride
2013-12-19 20:45                     ` Richard Miller
2013-12-20 15:23                       ` Aram Hăvărneanu
2013-12-19 19:12             ` Skip Tavakkolian
2013-12-19 19:22               ` Blake McBride
2013-12-19 19:43                 ` Rudolf Sykora
2013-12-19 19:58                   ` Blake McBride
2013-12-19 19:26             ` sl
2013-12-19 10:01     ` Richard Miller
2013-12-19 15:01       ` erik quanstrom
     [not found] <CAC0DbM5safEHO_MFpBazvvH6CcGQXGTow-Fe7fkqkP6GrU1Xzw@mail.gmail.com>
     [not found] ` <CAC0DbM7S-xZvOSDwB6KoWH2X8ny_57F9mBE7gaB_BuWR5RSJiw@mail.gmail.com>
2013-12-18 23:09   ` Jason Catena
2013-12-19  5:47     ` 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=3e1e9e6fbfa856a01013a2f51b8d244f@coraid.com \
    --to=quanstro@labs.coraid.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).