From: der.herr@hofr.at (Nicholas Mc Guire)
To: kernelnewbies@lists.kernelnewbies.org
Subject: remote system call
Date: Sat, 12 Mar 2016 17:00:20 +0000 [thread overview]
Message-ID: <20160312170020.GC3854@osadl.at> (raw)
In-Reply-To: <80466.1457215087@turing-police.cc.vt.edu>
On Sat, Mar 05, 2016 at 04:58:07PM -0500, Valdis.Kletnieks at vt.edu wrote:
> On Sat, 05 Mar 2016 15:58:13 +0530, Nitin Varyani said:
> > Codes are huge and documentation is negligible. How can I separate whay I
> > want to achieve from that big code?
>
> Why do you think that's possible?
>
> It's a lot more complicated problem to solve than you think. Maybe
> that huge code is necessary to achieve what you are trying to do.
>
check bproc - it was a relatively simple solution (with some limitations)
far simpler than MOSIX - for 2.6.X kernels it worked really nicely
but Im not aware of the status http://bproc.sourceforge.net/
seems to be a bit dated.
thx!
hofrat
prev parent reply other threads:[~2016-03-12 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 11:12 remote system call Nitin Varyani
2016-03-03 16:37 ` Mulyadi Santosa
2016-03-05 10:28 ` Nitin Varyani
2016-03-05 21:58 ` Valdis.Kletnieks at vt.edu
2016-03-12 17:00 ` Nicholas Mc Guire [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=20160312170020.GC3854@osadl.at \
--to=der.herr@hofr.at \
--cc=kernelnewbies@lists.kernelnewbies.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).