9front - general discussion about 9front
 help / color / mirror / Atom feed
From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: 9p2000.ix (Was Re: [9front] hackathon writeup)
Date: Thu, 13 Oct 2022 22:45:06 -0700	[thread overview]
Message-ID: <94F700F55A896082CE708F97BD64CE2C@smtp.pobox.com> (raw)
In-Reply-To: <DC490D1CB150DC590E317B5ED66FD09D@eigenstate.org>

Quoth ori@eigenstate.org:
> Quoth Jacob Moody <moody@mail.posixcafe.org>:
> > On 8/18/22 17:33, Stuart Morrow wrote:
> > > On 19/08/2022, Kurt H Maier <khm@sciops.net> wrote:
> > >> Where in the tree is it?   Their commit history is a disaster area and
> > >> there doesn't seem to be any explicit reference to it, nor documentation
> > >> regarding it.
> > > 
> > > Errrrr, devmnt?
> > 
> > https://github.com/fjballest/nixMarkIV/blob/master/port/devmnt.c
> > 
> > I think you're talking about this? Based on the context you seem
> > to be talking about it in.

It's also in his nix.markII repo.

Doing a diff of devmnt.c found in nix.markII and 9front's latest
devmnt.c doesn't look too wild, but I have yet to look at the other
affected files mentioned in Nemo's article.

> 
> see also:
> 
> 	https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.466.4876&rep=rep1&type=pdf

https://lsub.org/books-papers/ also have some related texts as well
(including the one ori mentioned).

I just saw https://linus.schreibt.jetzt/posts/qemu-9p-performance.html
on hackernews, which reminded me of this thread.



  reply	other threads:[~2022-10-14  5:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17  3:27 [9front] hackathon writeup ori
2022-08-18 22:37 ` Stuart Morrow
2022-08-18 22:52 ` Stuart Morrow
2022-08-18 23:09   ` Stanley Lieber
2022-08-18 23:32     ` Stuart Morrow
2022-08-18 23:11   ` Kurt H Maier
2022-08-18 23:33     ` Stuart Morrow
2022-08-18 23:55       ` Jacob Moody
2022-08-19  0:05         ` ori
2022-10-14  5:45           ` unobe [this message]
2022-08-19 11:34         ` Stuart Morrow
2022-08-19 13:21           ` Jacob Moody
2022-08-18 23:04 ` Stuart Morrow
2022-08-18 23:24   ` ori
2022-08-18 23:37     ` Stuart Morrow
2022-08-18 23:43       ` ori
2022-08-19  0:02       ` Kurt H Maier
2022-08-19  0:23         ` qwx
2022-08-19  1:54           ` Kurt H Maier
2022-08-19  2:02             ` qwx
2022-08-19  7:08         ` Steve Simon
2022-08-20  1:38           ` Xiao-Yong Jin
2022-08-20  3:57             ` ori
2022-08-19 19:52         ` Thaddeus Woskowiak
2022-08-19 21:13           ` David Arnold
2022-08-19 19:11   ` Aram Hăvărneanu
2022-08-19 20:40     ` Stuart Morrow
2022-08-20 13:14       ` Stuart Morrow
2022-08-22 17:54         ` Aram Hăvărneanu
2022-08-22 17:56           ` Kurt H Maier

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=94F700F55A896082CE708F97BD64CE2C@smtp.pobox.com \
    --to=unobe@cpan.org \
    --cc=9front@9front.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).