summaryrefslogtreecommitdiff
path: root/glibc/select.mdwn
blob: bafda141651475825b2bac5bf7861b830ae7bd85 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
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