Date: Tue, 15 Jun 2021 23:11:07 -0700 From: "Ronald F. Guilmette" <rfg@tristatelogic.com> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Is a successful call to write(2) atomic? Message-ID: <27579.1623823867@segfault.tristatelogic.com> In-Reply-To: <CAFbbPuhdNw4pQjKNyHnLpoNTkuxdr9=YcP%2BNQUTojz2eJnHfXg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <CAFbbPuhdNw4pQjKNyHnLpoNTkuxdr9=3DYcP+NQUTojz2eJnHfXg@mail.gma=
il.com>
Paul Procacci <pprocacci@gmail.com> wrote:
>This is what I was advocating for. Sorry if that wasn't clear.
>It might make sense to provide a visual representation using C pseudo cod=
e:
>{... snipped...}
Thank you Paul. I have the general idea, and I can take it from here.
Note that I was -already- having the master/parent process read input
and then pass down bits of work-to-be-done to the various "worker bee"
child proceses, so I do understand how to code all this up properly.
Now I just have to add in some more pipes to pass lines of completed
results back up to the parent, in addition to the parent sending stuff
down to the children via pipes.
Piece of cake. I just hope and trust (and believe) that adding that into
my existing code will solve the problem. I think it will.
Regards,
rfg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27579.1623823867>