| /kernel/linux/linux-4.19/drivers/scsi/mpt3sas/ |
| D | Kconfig | 32 # DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND
59 MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this
60 can be 256. However, it may decreased down to 16. Decreasing this
71 MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this
72 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-4.19/Documentation/powerpc/ |
| D | pmu-ebb.txt | 33 events, however unless the target process enables EBBs (via mtspr(BESCR)) no
47 It is however safe to run 'perf' commands on a process which is using EBBs. The
93 However, due to the design of the perf_events API, enabling an event does not
101 this case the enable will be successful. However if there is already an event
108 It is possible to read() from an EBB event. However the results are
124 The EBB handler is just regular userspace code, however it must be written in
|
| /kernel/linux/linux-4.19/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 some reservations m…
154 However, within those routines the code is simply checking to ensure there
205 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-4.19/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-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-4.19/include/linux/ |
| D | rculist_nulls.h | 29 * hlist_nulls_del_rcu(), running on this same list. However, it is
62 * However, it is perfectly legal to run concurrently with
85 * However, it is perfectly legal to run concurrently with
116 * However, it is perfectly legal to run concurrently with
|
| D | rculist_bl.h | 43 * hlist_bl_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
|
| /kernel/linux/linux-4.19/drivers/misc/echo/ |
| D | echo.h | 53 well. However, it only works well for signals of constant amplitude. It works
60 FAP, etc. Some perform significantly better than NLMS. However, factors such
65 the NLMS algorithm works very well. However, speech has more low frequency than
108 assess whether that signal contains a strong far end component. However, by the
|
| /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-4.19/Documentation/filesystems/ext4/ondisk/ |
| D | bigalloc.rst | 9 exceeds the page size. However, for a filesystem of mostly huge files,
17 however, the minimum allocation unit becomes a cluster, not a block,
|
| /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-4.19/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-4.19/Documentation/i2c/ |
| D | gpio-fault-injection | 34 core (see 'struct bus_recovery_info'). However, the bus recovery will not
60 recovery. This time, however, it should succeed and the device should release
70 because it acknowledges data. However, there are two differences compared to
|
| /kernel/linux/linux-4.19/Documentation/acpi/ |
| D | acpi-lid.txt | 16 reliable. However, there are exceptions. In order to work with these
25 However the word of "current" has ambiguity, some buggy AML tables return
55 triggered events to the userspace. However, given the fact that the buggy
|
| /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-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-4.19/Documentation/filesystems/ |
| D | fscrypt.rst | 30 However, except for filenames, fscrypt does not encrypt filesystem
101 However, userspace would need to do its part as well.)
180 However, it is nonstandard and has some problems such as being
200 to individual filesystems. However, authenticated encryption (AE)
216 used. However, each encrypted directory uses a unique key, which
228 block size, i.e. 16 bytes. However, the minimum size that can be
285 FS_IOC_SET_ENCRYPTION_POLICY is executed. However, it must be added
390 with a filesystem-specific prefix such as "ext4:". However, the
423 after all, the encryption is intended to be transparent. However,
429 enforcement`_. Attempts to do so will fail with EXDEV. However,
[all …]
|
| /kernel/linux/linux-4.19/fs/xfs/ |
| D | Kconfig | 21 module will be called xfs. Be aware, however, that if the file
96 filesystem to go down. However, it requires that the filesystem be
116 However, similar to XFS_DEBUG, it is only advisable to use this if you
|
| /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
|
| /kernel/linux/linux-4.19/Documentation/hid/ |
| D | hid-transport.txt | 91 multiplex all four on a single physical channel. However, in this document we
156 return the current report state of the device. However, OUTPUT reports as
161 according to the given data. Any of the 3 report types can be used. However,
164 A device must answer with a synchronous acknowledgement. However, HID core
231 drivers can choose to setup their device in this callback. However, normally
247 However, once ->open() is called, transport drivers must be ready for I/O.
255 ->open() calls have been followed by a ->close() call. However, ->start() may
|