Searched +full:two +full:- +full:user (Results 1 – 25 of 1047) sorted by relevance
12345678910>>...42
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | af_xdp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 XDP programs to redirect frames to a memory buffer in a user-space
24 syscall. Associated with each XSK are two rings: the RX ring and the
38 is simply an offset within the entire UMEM region. The user space
42 UMEM also has two rings: the FILL ring and the COMPLETION ring. The
47 kernel has transmitted completely and can now be used again by user
59 corresponding two rings, sets the XDP_SHARED_UMEM flag in the bind
64 single-consumer / single-producer (for performance reasons), the new
72 user-space application can place an XSK at an arbitrary place in this
79 traffic to user space through the XSK.
[all …]
|
| D | xfrm_sync.txt | 16 This way a backup stays as closely up-to-date as an active member.
20 For this reason, we also add a nagle-like algorithm to restrict
23 These thresholds are set system-wide via sysctls or can be updated
27 - the lifetime byte counter
31 - the replay sequence for both inbound and outbound
34 ----------------------
36 nlmsghdr:aevent_id:optional-TLVs.
43 A XFRM_MSG_NEWAE will have at least two TLVs (as is
69 message (kernel<->user) as well the cause (config, query or event).
74 when going from kernel to user space)
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | xfrm_sync.rst | 1 .. SPDX-License-Identifier: GPL-2.0
21 This way a backup stays as closely up-to-date as an active member.
25 For this reason, we also add a nagle-like algorithm to restrict
28 These thresholds are set system-wide via sysctls or can be updated
32 - the lifetime byte counter
36 - the replay sequence for both inbound and outbound
39 ----------------------
41 nlmsghdr:aevent_id:optional-TLVs.
49 A XFRM_MSG_NEWAE will have at least two TLVs (as is
76 message (kernel<->user) as well the cause (config, query or event).
[all …]
|
| D | af_xdp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 XDP programs to redirect frames to a memory buffer in a user-space
24 syscall. Associated with each XSK are two rings: the RX ring and the
38 is simply an offset within the entire UMEM region. The user space
42 UMEM also has two rings: the FILL ring and the COMPLETION ring. The
47 kernel has transmitted completely and can now be used again by user
59 corresponding two rings, sets the XDP_SHARED_UMEM flag in the bind
64 single-consumer / single-producer (for performance reasons), the new
72 user-space application can place an XSK at an arbitrary place in this
79 traffic to user space through the XSK.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/namespaces/ |
| D | compatibility-list.txt | 3 This document contains the information about the problems user
10 UTS IPC VFS PID User Net
15 User 2 2 X
28 2. Intentionally, two equal user IDs in different user namespaces
30 words, user 10 in one user namespace shouldn't have the same
31 access permissions to files, belonging to user 10 in another
34 The same is true for the IPC namespaces being shared - two users
35 from different user namespaces should not access the same IPC objects
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/namespaces/ |
| D | compatibility-list.rst | 5 This document contains the information about the problems user
13 - UTS IPC VFS PID User Net
19 User 2 2 X
33 2. Intentionally, two equal user IDs in different user namespaces
35 words, user 10 in one user namespace shouldn't have the same
36 access permissions to files, belonging to user 10 in another
39 The same is true for the IPC namespaces being shared - two users
40 from different user namespaces should not access the same IPC objects
|
| /kernel/linux/linux-5.10/Documentation/gpu/ |
| D | komeda-kms.rst | 1 .. SPDX-License-Identifier: GPL-2.0
23 -----
30 ------
39 -------------------
43 user can also insert a scaler between compositor and wb_layer to down scale
47 --------------------------
52 -----------------------------
57 --------------------------------
62 ------
66 introduces Layer Split, which splits the whole image to two half parts and feeds
[all …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | padata.rst | 1 .. SPDX-License-Identifier: GPL-2.0
23 ------------
43 ------------------
45 The CPUs used to run jobs can be changed in two ways, programatically with
58 live in /sys/kernel/pcrypt/<instance-name>. Within an instance's directory
59 there are two files, parallel_cpumask and serial_cpumask, and either cpumask
64 Reading one of these files shows the user-supplied cpumask, which may be
67 Padata maintains two pairs of cpumasks internally, the user-supplied cpumasks
69 cpumask.) The user-supplied cpumasks default to all possible CPUs on instance
71 subset of the user-supplied cpumasks and contain only the online CPUs in the
[all …]
|
| D | cachetlb.rst | 19 if it can be proven that a user address space has never executed
25 virtual-->physical address translations obtained from the software
43 This interface flushes an entire user address space from
56 Here we are flushing a specific range of (user) virtual
59 modifications for the address space 'vma->vm_mm' in the range
60 'start' to 'end-1' will be visible to the cpu. That is, after
62 virtual addresses in the range 'start' to 'end-1'.
78 address space is available via vma->vm_mm. Also, one may
79 test (vma->vm_flags & VM_EXEC) to see if this region is
81 split-tlb type setups).
[all …]
|
| /kernel/linux/linux-5.10/drivers/thermal/intel/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
8 enforce idle time which results in more package C-state residency. The
9 user interface is exposed via generic thermal framework.
20 two trip points which can be set by user to get notifications via thermal
40 temperature sensor (DTS). These SoCs have two additional DTSs in
42 thermal zone. There are two trip points. One of the trip point can
43 be set by user mode programs to get notifications via Linux thermal
52 temperature sensor (DTS). For X1000 SoC, it has one on-die DTS.
53 The DTS will be registered as a thermal zone. There are two trip points:
|
| /kernel/linux/linux-4.19/Documentation/ia64/ |
| D | efirtc.txt | 2 -------------------------------
9 the IA-64 platform.
11 The purpose of this driver is to supply an API for kernel and user applications
26 Because we wanted to minimize the impact on existing user-level apps using
34 the reference date is different. Year is the using the full 4-digit format.
39 without necessarily impacting any of the user applications. The decoupling
42 The driver exposes two interfaces, one via the device file and a set of
43 ioctl()s. The other is read-only via the /proc filesystem.
49 "public" API of the two drivers. The specifics of the legacy RTC are still
56 Two ioctl()s, compatible with the legacy RTC calls:
[all …]
|
| /kernel/linux/linux-4.19/Documentation/hwmon/ |
| D | adm9240 | 7 Addresses scanned: I2C 0x2c - 0x2f
13 Addresses scanned: I2C 0x2c - 0x2f
15 http://pdfserv.maxim-ic.com/en/ds/DS1780.pdf
19 Addresses scanned: I2C 0x2c - 0x2f
31 ---------
33 chip MSB 5-bit address. Each chip reports a unique manufacturer
37 -----------
39 microprocessor-based systems, providing measurement and limit comparison
40 of up to four power supplies and two processor core voltages, plus
41 temperature, two fan speeds and chassis intrusion. Measured values can
[all …]
|
| /kernel/linux/linux-4.19/Documentation/core-api/ |
| D | cachetlb.rst | 19 if it can be proven that a user address space has never executed
25 virtual-->physical address translations obtained from the software
43 This interface flushes an entire user address space from
56 Here we are flushing a specific range of (user) virtual
59 modifications for the address space 'vma->vm_mm' in the range
60 'start' to 'end-1' will be visible to the cpu. That is, after
62 virtual addresses in the range 'start' to 'end-1'.
78 address space is available via vma->vm_mm. Also, one may
79 test (vma->vm_flags & VM_EXEC) to see if this region is
81 split-tlb type setups).
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ia64/ |
| D | efirtc.rst | 13 the IA-64 platform.
15 The purpose of this driver is to supply an API for kernel and user applications
31 Because we wanted to minimize the impact on existing user-level apps using
39 the reference date is different. Year is the using the full 4-digit format.
44 without necessarily impacting any of the user applications. The decoupling
47 The driver exposes two interfaces, one via the device file and a set of
48 ioctl()s. The other is read-only via the /proc filesystem.
54 "public" API of the two drivers. The specifics of the legacy RTC are still
62 Two ioctl()s, compatible with the legacy RTC calls:
90 Those two ioctl()s can be exercised with the hwclock command:
[all …]
|
| /kernel/linux/linux-4.19/Documentation/kbuild/ |
| D | kconfig-macro-language.txt | 2 -------
5 two languages in one. One language describes dependency graphs consisting of
9 There is clear distinction between the two language stages. For example, you
17 $(CC) -o $(APP) $(SRC)
23 gcc -o foo foo.c
28 The idea is quite similar in Kconfig - it is possible to describe a Kconfig
34 def_bool $(shell, $(srctree)/scripts/gcc-check-foo.sh $(CC))
42 Then, Kconfig moves onto the evaluation stage to resolve inter-symbol
43 dependency as explained in kconfig-language.txt.
47 ---------
[all …]
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 6 -------
9 two languages in one. One language describes dependency graphs consisting of
13 There is clear distinction between the two language stages. For example, you
21 $(CC) -o $(APP) $(SRC)
27 gcc -o foo foo.c
32 The idea is quite similar in Kconfig - it is possible to describe a Kconfig
38 def_bool $(shell, $(srctree)/scripts/gcc-check-foo.sh $(CC))
46 Then, Kconfig moves onto the evaluation stage to resolve inter-symbol
47 dependency as explained in kconfig-language.rst.
51 ---------
[all …]
|
| /kernel/linux/linux-4.19/Documentation/acpi/ |
| D | video_extension.txt | 13 1 Export a sysfs interface for user space to control backlight level
22 Documentation/ABI/stable/sysfs-class-backlight.
56 The first two levels are for when laptop are on AC or on battery and are
61 as a "brightness level" indicator. Thus from the user space perspective
65 2 Notify user space about hotkey event
67 There are generally two cases for hotkey event reporting:
68 i) For some laptops, when user presses the hotkey, a scancode will be
69 generated and sent to user space through the input device created by
71 following key code will appear to user space:
84 notify value it received and send the event to user space through the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| D | strategies.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 The Linux kernel supports two major high-level power management strategies.
15 One of them is based on using global low-power states of the whole system in
16 which user space code cannot be executed and the overall system activity is
17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
18 kernel puts the system into one of these states when requested by user space
21 user space code can run. Because sleep states are global and the whole system
23 :doc:`system-wide power management <system-wide>`.
25 The other strategy, referred to as the :doc:`working-state power management
26 <working-state>`, is based on adjusting the power states of individual hardware
[all …]
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/pm/ |
| D | strategies.rst | 9 The Linux kernel supports two major high-level power management strategies.
11 One of them is based on using global low-power states of the whole system in
12 which user space code cannot be executed and the overall system activity is
13 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
14 kernel puts the system into one of these states when requested by user space
17 user space code can run. Because sleep states are global and the whole system
19 :doc:`system-wide power management <system-wide>`.
21 The other strategy, referred to as the :doc:`working-state power management
22 <working-state>`, is based on adjusting the power states of individual hardware
30 are inactive, ideally, they should be in low-power states in which they may not
[all …]
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | adm9240.rst | 10 Addresses scanned: I2C 0x2c - 0x2f
20 Addresses scanned: I2C 0x2c - 0x2f
24 http://pdfserv.maxim-ic.com/en/ds/DS1780.pdf
30 Addresses scanned: I2C 0x2c - 0x2f
37 - Frodo Looijaard <frodol@dds.nl>,
38 - Philip Edelbrock <phil@netroedge.com>,
39 - Michiel Rook <michiel@grendelproject.nl>,
40 - Grant Coady <gcoady.lk@gmail.com> with guidance
44 ---------
46 chip MSB 5-bit address. Each chip reports a unique manufacturer
[all …]
|
| /kernel/linux/linux-4.19/Documentation/thermal/ |
| D | x86_pkg_temperature_thermal | 11 ---
12 Intel® 64 and IA-32 Architectures Software Developer’s Manual (Jan, 2013):
16 ---------
19 zone with maximum two user mode configurable trip points. Number of trip points
21 user mode can receive notification via thermal notification mechanism and can
26 --------------------
31 This contains two trip points:
32 - trip_point_0_temp
33 - trip_point_1_temp
35 User can set any temperature between 0 to TJ-Max temperature. Temperature units
[all …]
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | active_mm.rst | 9 List: linux-kernel
12 Date: 1999-07-30 21:36:24
14 Cc'd to linux-kernel, because I don't write explanations all that often,
21 > discussed on the mailing lists---I just returned from vacation and
22 > wasn't able to follow linux-kernel for a while).
26 - we have "real address spaces" and "anonymous address spaces". The
28 user-level page tables at all, so when we do a context switch into an
33 doesn't need any user mappings - all kernel threads basically fall into
35 some amount of time they are not going to be interested in user space,
37 switching the VM state around. Currently only the old-style bdflush
[all …]
|
| /kernel/linux/linux-4.19/Documentation/vm/ |
| D | active_mm.rst | 9 List: linux-kernel
12 Date: 1999-07-30 21:36:24
14 Cc'd to linux-kernel, because I don't write explanations all that often,
21 > discussed on the mailing lists---I just returned from vacation and
22 > wasn't able to follow linux-kernel for a while).
26 - we have "real address spaces" and "anonymous address spaces". The
28 user-level page tables at all, so when we do a context switch into an
33 doesn't need any user mappings - all kernel threads basically fall into
35 some amount of time they are not going to be interested in user space,
37 switching the VM state around. Currently only the old-style bdflush
[all …]
|
| /kernel/linux/linux-4.19/arch/powerpc/include/asm/nohash/32/ |
| D | pte-8xx.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
8 * We also use the two level tables, but we can put the real bits in them
12 * based upon user/super access. The TLB does not have accessed nor write
15 * two bits in the software pte that are supposed to be set to zero in
23 * Large page sizes added. We currently support two sizes, 4K and 8M.
46 #define _PAGE_NA 0x0200 /* Supervisor NA, User no access */
47 #define _PAGE_RO 0x0600 /* Supervisor RO, User no access */
|
| /kernel/linux/linux-4.19/drivers/usb/gadget/legacy/ |
| D | Kconfig | 6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
8 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
9 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
10 # - Some systems have both kinds of controllers.
12 # With help from a special transceiver and a "Mini-AB" jack, systems with
13 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
21 Gadget Zero is a two-configuration device. It either sinks and
24 conformance. The driver needs only two bulk-capable endpoints, so
25 it can work on top of most device-side usb controllers. It's
30 USB peripheral controller driver. Then you can use host-side
[all …]
|
12345678910>>...42