summaryrefslogtreecommitdiff
path: root/glibc/select.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'glibc/select.mdwn')
-rw-r--r--glibc/select.mdwn25
1 files changed, 25 insertions, 0 deletions
diff --git a/glibc/select.mdwn b/glibc/select.mdwn
new file mode 100644
index 00000000..bafda141
--- /dev/null
+++ b/glibc/select.mdwn
@@ -0,0 +1,25 @@
+[[!meta copyright="Copyright © 2012 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
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!tag open_issue_documentation]]
+
+
+# IRC, freenode, #hurd, 2012-08-10
+
+ <afleck> what is the use of having a port set name that can receive from
+ multiple ports?
+ <youpi> think of select()
+ <afleck> I haven't really gotten into it yet, I was just reading the Mach
+ Kernel Guide and I didn't understand the difference between having a port
+ set and multiple ports, since you can't choose which port receives in a
+ port set.
+ <youpi> with multiple ports, you'd have to have as many threads to block in
+ reception
+ <youpi> or poll in turn