Searched refs:userspace (Results 1 – 25 of 342) sorted by relevance
12345678910>>...14
| /linux-3.4.99/Documentation/networking/ |
| D | mac80211-auth-assoc-deauth.txt | 9 participant userspace
14 userspace->mac80211: authenticate
44 mac80211->userspace: RX auth frame
48 userspace->mac80211: associate
75 mac80211->userspace: associated
77 note left of userspace: associated now
80 note over userspace
84 userspace->mac80211: authorized
88 userspace->mac80211: deauthenticate/disassociate
99 mac80211->userspace: disconnected
|
| D | openvswitch.txt | 4 The Open vSwitch kernel module allows flexible userspace control over
13 table" that userspace populates with "flows" that map from keys based
21 no match, it queues the packet to userspace for processing (as part of
22 its processing, userspace will likely set up a flow to handle further
35 to Open vSwitch is designed to allow carefully written userspace
39 kernel module passes a packet to userspace, it also passes along the
44 - If userspace's notion of the flow key for the packet matches the
47 - If the kernel's flow key includes more fields than the userspace
49 headers but userspace stopped at the Ethernet type (because it
54 - If the userspace flow key includes more fields than the
[all …]
|
| D | operstates.txt | 15 Thanks to 802.1X, userspace must be granted the possibility to
19 and changeable from userspace under certain rules.
22 2. Querying from userspace
26 to be notified of updates. This is important for setting from userspace.
46 Interface is in unknown state, neither driver nor userspace has set
70 contains link policy. This is needed for userspace interaction
117 IF_OPER_UP if userspace interaction is disabled. Otherwise
118 IF_OPER_DORMANT with the possibility for userspace to initiate the
122 4. Setting from userspace
129 driver. Afterwards, the userspace application can set IFLA_OPERSTATE
[all …]
|
| D | dns_resolver.txt | 21 upcalled to userspace through /sbin/request-key.
23 These routines must be supported by userspace tools dns.upcall, cifs.upcall and
27 (*) Implements the dns_resolver key_type to contact userspace.
77 it doesn't find it, it upcalls to userspace to make a new DNS query, which
114 Keys of dns_resolver type can be read from userspace using keyctl_read() or
123 this type are used to transport and cache DNS lookup results from userspace.
127 userspace to get a new result.
129 Upcalls to userspace are made through the request_key() upcall vector, and are
|
| /linux-3.4.99/Documentation/device-mapper/ |
| D | dm-log.txt | 23 userspace drivers/md/dm-log-userspace* include/linux/dm-log-userspace.h
37 The "userspace" log type
39 This log type simply provides a way to export the log API to userspace,
41 logging requests to userspace, where a daemon receives and processes the
44 The structure used for communication between kernel and userspace are
45 located in include/linux/dm-log-userspace.h. Due to the frequency,
47 kernel and userspace, 'connector' is used as the interface for
50 There are currently two userspace log implementations that leverage this
|
| /linux-3.4.99/Documentation/infiniband/ |
| D | user_verbs.txt | 4 enables direct userspace access to IB hardware via "verbs," as
11 userspace driver for your InfiniBand hardware. For example, to use
13 libmthca userspace driver be installed.
20 directly to hardware registers mmap()ed into userspace, with no
27 Status is returned to userspace as the return value of the write()
34 of which resources are attached to a given userspace context. The
36 between kernel pointers and opaque userspace handles, so that kernel
37 pointers are never exposed to userspace and userspace cannot trick
45 Direct userspace I/O requires that memory regions that are potential
67 and so on. Since the InfiniBand userspace verbs should be safe for
|
| /linux-3.4.99/drivers/infiniband/ |
| D | Kconfig | 14 tristate "InfiniBand userspace MAD support"
18 is the kernel side of the userspace MAD support, which allows
19 userspace processes to send and receive MADs. You will also
23 tristate "InfiniBand userspace access (verbs and CM)"
27 kernel side of userspace verbs and the userspace
28 communication manager (CM). This allows userspace processes
|
| /linux-3.4.99/drivers/connector/ |
| D | Kconfig | 3 tristate "Connector - unified userspace <-> kernelspace linker"
6 This is unified userspace <-> kernelspace connector working on top
15 boolean "Report process events to userspace"
19 Provide a connector that reports process events to userspace. Send
|
| /linux-3.4.99/Documentation/ABI/testing/ |
| D | sysfs-gpio | 8 userspace. GPIOs are only made available to userspace by an explicit
10 kernel code, it may be exported by userspace (and unexported later).
17 /export ... asks the kernel to export a GPIO to userspace
|
| /linux-3.4.99/Documentation/accounting/ |
| D | taskstats.txt | 6 per-process statistics from the kernel to userspace.
29 To get statistics during a task's lifetime, userspace opens a unicast netlink
34 To obtain statistics for tasks which are exiting, the userspace listener
42 an additional record containing the per-tgid stats is also sent to userspace.
80 the task/process for which userspace wants statistics.
87 the cpumask would be "1-3,5,7-8". If userspace forgets to deregister interest
92 2. Response for a command: sent from the kernel in response to a userspace
120 stats in userspace alone is inefficient and potentially inaccurate (due to lack
127 gets sent to userspace (along with the per-task data).
146 interface to return them. Since userspace processes each netlink attribute
[all …]
|
| /linux-3.4.99/drivers/md/ |
| D | Makefile | 11 dm-log-userspace-y \
12 += dm-log-userspace-base.o dm-log-userspace-transfer.o
42 obj-$(CONFIG_DM_LOG_USERSPACE) += dm-log-userspace.o
|
| /linux-3.4.99/drivers/uio/ |
| D | Kconfig | 5 Enable this to allow the userspace driver core code to be
6 built. This code allows userspace programs easy access to
8 to be written in userspace. Note that a small kernel driver
20 driver requires a userspace component called cif that handles
40 This kernel driver requires that the matching userspace driver
69 Automata GmbH. The userspace part of this driver will be
91 This driver requires a userspace component that comes with the card
|
| /linux-3.4.99/drivers/w1/ |
| D | Kconfig | 20 This allows to communicate with userspace using connector. For more
22 There are three types of messages between w1 core and userspace:
26 3. Replies to userspace commands.
|
| /linux-3.4.99/drivers/gpu/drm/radeon/ |
| D | Kconfig | 12 cause issues or bugs compared to the previous userspace driver stack.
18 KMS enabled userspace will use new API to talk with the radeon/drm
21 (here TTM). In order to submit command to the GPU the userspace
23 userspace have to provide a list of buffer object used by the
|
| /linux-3.4.99/Documentation/w1/ |
| D | w1.netlink | 7 There are three types of messages between w1 core and userspace:
11 3. Replies to userspace commands.
28 userspace command for bus master
31 userspace command for slave device
48 (write and sample data back to userspace)
67 Currently replies to userspace commands are only generated for read
79 Replies to W1_LIST_MASTERS should send a message back to the userspace
175 Sequence number for userspace requests is set by userspace application.
185 This archive includes userspace application w1d.c which uses
|
| /linux-3.4.99/Documentation/powerpc/ |
| D | kvm_440.txt | 6 To enforce isolation, host userspace, guest kernel, and guest userspace all
13 The usual code flow is started from userspace invoking an "run" ioctl, which
19 - return to host userspace (e.g. when the guest performs device MMIO)
38 IO: MMIO and DCR accesses are emulated by userspace. We use virtio for network
|
| /linux-3.4.99/drivers/sh/intc/ |
| D | Kconfig | 7 This enables support for hardware-assisted userspace hardirq
12 userspace. This is primarily for use by userspace device
|
| /linux-3.4.99/drivers/staging/panel/ |
| D | TODO | 5 - review userspace api
6 - see if all of this could be easier done in userspace instead.
|
| /linux-3.4.99/drivers/staging/frontier/ |
| D | TODO | 4 - fix userspace interface to be sane
5 - possibly just port to userspace with libusb
|
| /linux-3.4.99/Documentation/early-userspace/ |
| D | README | 1 Early userspace support
7 "Early userspace" is a set of libraries and programs that provide
19 - klibc, a userspace C library, currently packaged separately, that is
24 two ways to add an early userspace image: specify an existing cpio
30 You can create a cpio archive that contains the early userspace image.
38 The kernel build process can also build an early userspace image from
65 early userspace image can be built by an unprivileged user.
85 early userspace useful. The klibc distribution is currently
109 move to early userspace:
122 For questions and help, you can sign up for the early userspace
|
| /linux-3.4.99/Documentation/filesystems/ |
| D | fuse.txt | 7 userspace process. The filesystem can be accessed normally through
16 A userspace filesystem mounted by a non-privileged (non-root) user.
40 FUSE is a userspace filesystem framework. It consists of a kernel
41 module (fuse.ko), a userspace library (libfuse.*) and a mount utility
49 The userspace library and utilities are available from the FUSE
75 The file descriptor to use for communication between the userspace
105 (userspace) configuration option.
136 userspace or being processed by the filesystem daemon. If there is
154 1) If the request is not yet sent to userspace AND the signal is
158 2) If the request is not yet sent to userspace AND the signal is not
[all …]
|
| /linux-3.4.99/Documentation/driver-model/ |
| D | device.txt | 96 device_remove_file() to be called on a device at any time, userspace has
98 registered in the kernel, a uevent is generated to notify userspace (like
100 device is registered, then userspace won't get notified and userspace will
106 userspace will never be notified of the new attributes.
|
| /linux-3.4.99/drivers/cpufreq/ |
| D | Kconfig | 12 (see below) after boot, or use a userspace tool.
71 bool "userspace"
74 Use the CPUFreq governor 'userspace' as default. This allows
75 you to set the CPU frequency manually or when a userspace
77 to enable the userspace governor manually.
127 tristate "'userspace' governor for userspace frequency scaling"
130 CPU frequency manually or when a userspace program shall
|
| /linux-3.4.99/Documentation/ |
| D | rfkill.txt | 34 replaced by userspace policy code) and
42 The rfkill core code also notifies userspace of state changes, and provides
43 ways for userspace to query the current states. See the "Userspace support"
87 The recommended userspace interface to use is /dev/rfkill, which is a misc
88 character device that allows userspace to obtain and set the state of rfkill
89 devices and sets of devices. It also notifies userspace about device addition
97 userspace is able to get a consistent snapshot of all rfkill devices in the
|
| /linux-3.4.99/Documentation/firmware_class/ |
| D | README | 23 userspace:
31 userspace:
38 userspace:
96 firmware reloaded, it won't be possible to get it from userspace.
107 persistent should be left to userspace.
|
12345678910>>...14