The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] XID register
Date: Sat, 2 Dec 2023 22:01:54 -0800	[thread overview]
Message-ID: <CAP6exYKEosAD90LFx6npZLEZmA2vMx3hF-Zdx-DAeuSfpUNAZA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 677 bytes --]

SunRPC, among other protocols, needs transaction IDs (XIDs) to distinguish
RPCs.For SunRPC, it's important that XIDs not be reused (not for all
protocols; 9p has no such requirement). Stateless protocols like NFS and
reused XIDs can get messy.

There is a vague, 30 year old memory, I have, that at some point SPARC got
a time register, or some other register, that always provided a different
answer each time it was read, even if read back to back, in part to enable
creation of non-reused XIDs. Note that things like the TSC or RISC-V MTIME
register make no such guarantee.

I am pretty sure someone here can fill me in, or tell me I'm wrong, about
my SPARC memory.

thanks

[-- Attachment #2: Type: text/html, Size: 780 bytes --]

             reply	other threads:[~2023-12-03  6:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03  6:01 ron minnich [this message]
2024-01-10  4:22 ` [TUHS] " Rico Pajarola

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=CAP6exYKEosAD90LFx6npZLEZmA2vMx3hF-Zdx-DAeuSfpUNAZA@mail.gmail.com \
    --to=rminnich@gmail.com \
    --cc=tuhs@tuhs.org \
    /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).