9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey100100100@gmail.com
To: 9fans@9fans.net
Subject: Re: [9fans] syscall silently kill processes
Date: Mon, 20 Jun 2022 00:26:48 +0300	[thread overview]
Message-ID: <714f4315abb5a095e98e8fbc8c1bd4dd031dee51.camel@gmail.com> (raw)
In-Reply-To: <86055e9ba3dbe8ef06764d6d674830a8ec9404fa.camel@gmail.com>

В Пн, 20/06/2022 в 00:22 +0300, andrey100100100@gmail.com пишет:
> В Вс, 19/06/2022 в 16:41 +0000, adr пишет:
> > On Sun, 19 Jun 2022, andrey100100100@gmail.com wrote:
> > > Yes, you were absolutely right, the thread library needs some
> > > work.
> > > 
> > > It is impossible to use multiple processes with notes, due to the
> > > exhaustion of the NFN limit.
> > 
> > Andrej, what are you going to do with alarm in the real thing?
> 
> The note 'alarm' is needed to interrupt the system call on timeout
> since system calls to lan 9 can be of a network nature, a notes is
> indispensable.
> A great example of this is the read() system call on a udp-
> connection.
> How else can this system call be interrupted?
> 
> 
> 
> > You could use threads (cooperative round-ribbon multitasking) using
> > some data log to register their state and use a "master" thread to
> > control them (kill them, change some data structure, etc).
> > 
> > You can use rfork, locks, pipes, etc and forget about libthread.


Channels are a good abstraction for exchanging data between processes.
Even if not to use the libthread, I would have to (probably) write it.
But yeah, maybe it's easier to do without it.

> > 
> > You could experiment with the topology of the nodes, for example
> > instead of a big star you can simplify things a lot using chains
> > of nodes where the last node sends the chain data to the analyzer
> > (you were talking about polling sensors):
> > 
> > aNode1 --> aNode2 --> aNode3 --> ... --> aNoden -->
> >                                                                    
> >   
> >                   > --- > Anz
> > bNode1 --> bNode2 --> bNode3 --> ... --> bNoden -->
> > 
> > Imagine that n=100. Each node only has to make a connection with
> > 2 nodes (the first of the chain just one), adding data to the
> > received one and send it to the next. Anz only has to make a
> > connection with the last nodes of the chains, two in this case,
> > and process the data received. Of course you have to play with your
> > numbers, the acceptable delay, etc.
> > 
> > I'm pretty sure people here could point you to some examples using
> > plan9, and note that you could use raspberry pi zeros as nodes.
> > 
> > Have fun.
> > 

Regards,
Andrej


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tfa6823048ad90a21-M06156a275c41ac100d18311b
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-06-19 21:27 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  9:37 andrey100100100
2022-06-17 13:46 ` Thaddeus Woskowiak
2022-06-17 14:11   ` Jacob Moody
2022-06-17 14:39     ` Thaddeus Woskowiak
2022-06-17 15:06     ` andrey100100100
2022-06-17 16:08       ` Skip Tavakkolian
2022-06-17 16:11         ` Skip Tavakkolian
2022-06-17 16:16           ` Skip Tavakkolian
2022-06-17 17:42             ` adr
2022-06-17 16:11       ` Jacob Moody
2022-06-17 18:48         ` andrey100100100
2022-06-17 19:28           ` Jacob Moody
2022-06-17 21:15           ` adr
2022-06-18  6:40             ` andrey100100100
2022-06-18  8:37               ` adr
2022-06-18  9:22                 ` adr
2022-06-18 12:53                   ` Jacob Moody
2022-06-18 22:03                     ` andrey100100100
2022-06-19  5:54                     ` adr
2022-06-19  6:13                       ` Jacob Moody
2022-06-18 22:22                   ` andrey100100100
2022-06-18 16:57                 ` andrey100100100
2022-06-19  2:40                   ` adr
2022-06-19  5:01                     ` adr
2022-06-19  8:52                       ` andrey100100100
2022-06-19 10:32                         ` adr
2022-06-19 11:40                           ` andrey100100100
2022-06-19 12:01                             ` andrey100100100
2022-06-19 15:10                           ` andrey100100100
2022-06-19 16:41                             ` adr
2022-06-19 21:22                               ` andrey100100100
2022-06-19 21:26                                 ` andrey100100100 [this message]
2022-06-20  4:41                                 ` adr
2022-06-20  5:39                                   ` andrey100100100
2022-06-20  5:59                                   ` adr
2022-06-20 15:56                                     ` andrey100100100
2022-06-20 22:29                                       ` Skip Tavakkolian
2022-06-21  7:07                                         ` andrey100100100
2022-06-21 11:26                                           ` adr
2022-06-21 13:03                                             ` andrey100100100
2022-06-21 13:22                                               ` adr
2022-06-28 15:28                                                 ` adr
2022-06-28 16:43                                                   ` ori
2022-06-28 18:19                                                   ` adr
2022-06-28 18:28                                                     ` adr
2022-06-28 19:09                                                   ` andrey100100100
2022-06-28 19:42                                                     ` adr
2022-06-29 13:14                                                       ` adr
2022-06-21 13:47                                             ` andrey100100100
2022-06-21  7:22                                         ` adr

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=714f4315abb5a095e98e8fbc8c1bd4dd031dee51.camel@gmail.com \
    --to=andrey100100100@gmail.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).