The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] V6 UNIX main() oddness
Date: Thu, 25 Jan 2018 14:41:16 -0500	[thread overview]
Message-ID: <CAC20D2MRr9ZcrLt4f6NddUUjCURqgdEygnxNAsr=QUM_Z2m29Q@mail.gmail.com> (raw)
In-Reply-To: <20180125184259.8B62518C0B0@mercury.lcs.mit.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]

Seems reasonable to me give the code path and time its being called.  Maybe
left over from hacking from an earlier kernel requirement and never noticed
by Ken.  I wonder if the mount table had been set up in some earlier scheme
and he wanted to make sure it was checked first.  That's the only thing
that seems logical, but we all miss optimizations.
ᐧ

On Thu, Jan 25, 2018 at 1:42 PM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:

> So, while bringing up V6 on a hardware PDP-11/23 with an RK11 emulator
> using
> an SD card for storage which Dave Bridgham and I are doing, I found this
> piece
> of code in main() on V6 Unix:
>
>         rootdir = iget(rootdev, ROOTINO);
>         rootdir->i_flag =& ~ILOCK;
>         u.u_cdir = iget(rootdev, ROOTINO);
>         u.u_cdir->i_flag =& ~ILOCK;
>
> I don't get why two separate calls to iget(), with the same arguments;
> why not replace the second pair of lines with:
>
>         u.u_cdir = rootdir;
>         rootdir->i_count++;
>
> What am I missing?
>
>         Noel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180125/745fbeda/attachment.html>


      parent reply	other threads:[~2018-01-25 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 18:42 Noel Chiappa
2018-01-25 19:36 ` Ron Natalie
2018-01-25 19:41 ` Clem Cole [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='CAC20D2MRr9ZcrLt4f6NddUUjCURqgdEygnxNAsr=QUM_Z2m29Q@mail.gmail.com' \
    --to=clemc@ccc.com \
    /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).