| /kernel/linux/linux-6.6/drivers/scsi/mpt3sas/ |
| D | Kconfig | 32 # DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND
60 MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this
61 can be 256. However, it may decreased down to 16. Decreasing this
72 MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this
73 can be 256. However, it may decreased down to 16. Decreasing this
|
| /kernel/linux/linux-5.10/drivers/scsi/mpt3sas/ |
| D | Kconfig | 32 # DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND
60 MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this
61 can be 256. However, it may decreased down to 16. Decreasing this
72 MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this
73 can be 256. However, it may decreased down to 16. Decreasing this
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| D | pmu-ebb.rst | 34 events, however unless the target process enables EBBs (via mtspr(BESCR)) no
48 It is however safe to run 'perf' commands on a process which is using EBBs. The
94 However, due to the design of the perf_events API, enabling an event does not
102 this case the enable will be successful. However if there is already an event
109 It is possible to read() from an EBB event. However the results are
125 The EBB handler is just regular userspace code, however it must be written in
|
| /kernel/linux/linux-6.6/Documentation/powerpc/ |
| D | pmu-ebb.rst | 34 events, however unless the target process enables EBBs (via mtspr(BESCR)) no
48 It is however safe to run 'perf' commands on a process which is using EBBs. The
94 However, due to the design of the perf_events API, enabling an event does not
102 this case the enable will be successful. However if there is already an event
109 It is possible to read() from an EBB event. However the results are
125 The EBB handler is just regular userspace code, however it must be written in
|
| /kernel/linux/linux-6.6/Documentation/gpu/rfc/ |
| D | xe.rst | 48 However, the force_probe mechanism existent in both drivers will allow only one
81 Xe primarily uses Firmware based scheduling (GuC FW). However, it will use
83 resolve syncobj and dma-buf implicit sync dependencies. However, drm_scheduler is
119 development of a common new drm_infrastructure. However, the Xe team needs to
151 However, there are more aspects around the rules for that and the usage of
181 in a next stage. However, this should not block the initial merge.
195 However, display code should not gate the acceptance of Xe in upstream. Xe
|
| /kernel/linux/linux-6.6/Documentation/mm/ |
| D | hugetlbfs_reserv.rst | 18 kernel, the code has evolved over time. However, the basic idea was to
139 always the value (to - from). However, for shared mappings it is possible that
153 However, within those routines the code is simply checking to ensure there
204 However, in every case the avoid_reserve argument overrides the use of
243 in the reserve map already existed so no change is made. However, if there
322 However, if reserves are associated with the subpool a return value less
407 return value of region_chg(). However, in the case of shared mappings it is
437 indicate that there is a reservation for the page. However, the subpool and
462 in the section "Reservation Map Modifications". However, they do take into
524 However, there are several instances where errors are encountered after a huge
[all …]
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | hugetlbfs_reserv.rst | 20 kernel, the code has evolved over time. However, the basic idea was to
141 always the value (to - from). However, for shared mappings it is possible that
155 However, within those routines the code is simply checking to ensure there
206 However, in every case the avoid_reserve argument overrides the use of
244 in the reserve map already existed so no change is made. However, if there
323 However, if reserves are associated with the subpool a return value less
408 return value of region_chg(). However, in the case of shared mappings it is
438 indicate that there is a reservation for the page. However, the subpool and
463 in the section "Reservation Map Modifications". However, they do take into
525 However, there are several instances where errors are encountered after a huge
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | perf.rst | 74 non-VHE guest however please note that EL2 is never counted within a guest.
81 transition at EL2 - however there is a period of time between
85 exclude_host. However when using !exclude_hv there is a small blackout
|
| /kernel/linux/linux-5.10/drivers/misc/echo/ |
| D | echo.h | 41 well. However, it only works well for signals of constant amplitude. It works
48 FAP, etc. Some perform significantly better than NLMS. However, factors such
53 the NLMS algorithm works very well. However, speech has more low frequency than
96 assess whether that signal contains a strong far end component. However, by the
|
| /kernel/linux/linux-6.6/drivers/misc/echo/ |
| D | echo.h | 41 well. However, it only works well for signals of constant amplitude. It works
48 FAP, etc. Some perform significantly better than NLMS. However, factors such
53 the NLMS algorithm works very well. However, speech has more low frequency than
96 assess whether that signal contains a strong far end component. However, by the
|
| /kernel/linux/linux-6.6/arch/alpha/include/uapi/asm/ |
| D | types.h | 9 * not a major issue. However, for interoperability, libraries still
18 * However, some user programs are fine with this. They can
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/qcom/ |
| D | msm8916-samsung-e7.dts | 14 * However, it is possible to use this device tree by compiling an ARM32 kernel
16 * to the other MSM8916 device trees. However, it is actually used through
|
| D | msm8916-samsung-e5.dts | 14 * However, it is possible to use this device tree by compiling an ARM32 kernel
16 * to the other MSM8916 device trees. However, it is actually used through
|
| /kernel/linux/linux-5.10/arch/alpha/include/uapi/asm/ |
| D | types.h | 9 * not a major issue. However, for interoperability, libraries still
18 * However, some user programs are fine with this. They can
|
| /kernel/linux/linux-6.6/drivers/hwmon/occ/ |
| D | Kconfig | 12 On-Chip Controller (OCC) on a POWER8 processor. However, this driver
26 On-Chip Controller (OCC) on a POWER9 processor. However, this driver
|
| /kernel/linux/linux-5.10/drivers/hwmon/occ/ |
| D | Kconfig | 13 On-Chip Controller (OCC) on a POWER8 processor. However, this driver
28 On-Chip Controller (OCC) on a POWER9 processor. However, this driver
|
| /kernel/linux/linux-6.6/tools/memory-model/Documentation/ |
| D | ordering.txt | 115 synchronize_srcu() and so on. However, these primitives have orders
184 the write to "y". However, you are usually better off using a release
216 "x". However, you are usually better off using an acquire load, as described
432 However, control dependencies are easily destroyed by compiler
452 However, if a group of CPUs apply these operations to a single variable,
462 a number of destructive optimizations. However, they provide no
470 a number of destructive optimizations. However, they provide no
483 However, many CPUs will happily reorder these operations with
554 fastpaths. However, the price is great care and continual attention
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | rculist_nulls.h | 29 * hlist_nulls_del_rcu(), running on this same list. However, it is
70 * However, it is perfectly legal to run concurrently with
93 * However, it is perfectly legal to run concurrently with
124 * However, it is perfectly legal to run concurrently with
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | rculist_nulls.h | 29 * hlist_nulls_del_rcu(), running on this same list. However, it is
70 * However, it is perfectly legal to run concurrently with
93 * However, it is perfectly legal to run concurrently with
124 * However, it is perfectly legal to run concurrently with
|
| /kernel/linux/linux-5.10/arch/powerpc/include/uapi/asm/ |
| D | types.h | 6 * not a major issue. However, for interoperability, libraries still
22 * However, some user programs are fine with this. They can
|
| /kernel/linux/linux-6.6/arch/powerpc/include/uapi/asm/ |
| D | types.h | 6 * not a major issue. However, for interoperability, libraries still
22 * However, some user programs are fine with this. They can
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | fscrypt.rst | 30 However, except for filenames, fscrypt does not encrypt filesystem
110 However, fscrypt allows encryption keys to be removed from the kernel,
120 However, these ioctls have some limitations:
142 to your kernel command line. However, this has a performance cost.
352 per-file encryption keys. However, it depends on the security of two
361 to individual filesystems. However, authenticated encryption (AE)
402 However, each encrypted directory still uses a unique key, or
414 >= 16 bytes; cipher block alignment is not required. However,
504 FS_IOC_SET_ENCRYPTION_POLICY is executed. However, it must be added
535 FS_IOC_SET_ENCRYPTION_POLICY is executing. However, if the new
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ |
| D | atomic_t.txt | 196 later accesses against the RMW op and all accesses preceding it. However,
218 However the atomic_fetch_add() might be implemented more efficiently.
321 operations -- those in the Arithmetic and Bitwise classes and xchg(). However
326 indefinitely. However, this is not evident on LL/SC architectures, because
356 However, even the forward branch from the failed compare can cause the LL/SC
|
| /kernel/linux/linux-6.6/Documentation/networking/device_drivers/can/ |
| D | can327.rst | 35 As such, can327 is a best effort driver. However, this is more than
210 However, immediately after sending a frame, the ELM327 will be in
238 However, they do send ACKs while waiting for a reply immediately
276 However there is an exception: With a separate flag, it may set the
293 helpful here, however SocketCAN does not currently provide a facility
|
| /kernel/linux/linux-5.10/Documentation/hid/ |
| D | hid-transport.rst | 95 multiplex all four on a single physical channel. However, in this document we
160 return the current report state of the device. However, OUTPUT reports as
165 according to the given data. Any of the 3 report types can be used. However,
168 A device must answer with a synchronous acknowledgement. However, HID core
239 drivers can choose to setup their device in this callback. However, normally
262 However, once ->open() is called, transport drivers must be ready for I/O.
274 ->open() calls have been followed by a ->close() call. However, ->start() may
|