diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2014-02-26 15:20:53 +0100 |
|---|---|---|
| committer | Thomas Schwinge <thomas@codesourcery.com> | 2014-02-26 15:20:53 +0100 |
| commit | 93060a3967ef66873d6246b0b1228c57aed2d9e4 (patch) | |
| tree | 0dda55d9eaa0fdf687acc80ac2329bdf42c6a652 /microkernel/mach/mig/documentation.mdwn | |
| parent | ca63bd2d33b3d28eabd50ad58577b52a1fc9eba0 (diff) | |
| parent | c4ad3f73033c7e0511c3e7df961e1232cc503478 (diff) | |
| download | web-93060a3967ef66873d6246b0b1228c57aed2d9e4.tar.gz web-93060a3967ef66873d6246b0b1228c57aed2d9e4.tar.bz2 web-93060a3967ef66873d6246b0b1228c57aed2d9e4.zip | |
Merge remote-tracking branch 'feldtkeller.SCHWINGE/master'
Conflicts:
news/2011-q2.mdwn
open_issues/glibc.mdwn
open_issues/versioning.mdwn
Diffstat (limited to 'microkernel/mach/mig/documentation.mdwn')
| -rw-r--r-- | microkernel/mach/mig/documentation.mdwn | 16 |
1 files changed, 14 insertions, 2 deletions
diff --git a/microkernel/mach/mig/documentation.mdwn b/microkernel/mach/mig/documentation.mdwn index e6bd1bb9..96731a5d 100644 --- a/microkernel/mach/mig/documentation.mdwn +++ b/microkernel/mach/mig/documentation.mdwn @@ -1,5 +1,5 @@ -[[!meta copyright="Copyright © 2002, 2003, 2005, 2007, 2008, 2009, 2010, 2013 -Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2002, 2003, 2005, 2007, 2008, 2009, 2010, 2013, +2014 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -99,3 +99,15 @@ pp. 67--77." <braunr> simple (but optimized) scatter-gather <braunr> it makes sense for mig since mach messages do include serialization metadata such as types + + +## IRC, freenode, #hurd, 2013-11-01 + + <gnu_srs> Is it possible to call server functions from user space? What + about functions returning MIG_NO_REPLY? + <neal> gnu_srs: server functions are only called from user space... + <neal> gnu_srs: Normally, servers use a server loop. When an RPC comes it, + it is processed and the processing returns some values that the server + loop returns to the client. + <neal> If the server wants to return the thread to the thread pool without + responding to the RPC, it uses MIG_NO_REPLY. |