Searched full:will (Results 276 – 300 of 20022) sorted by relevance
1...<<11121314151617181920>>...801
| /linux-6.15/Documentation/scsi/ |
| D | scsi_fc_transport.rst | 51 interact with the Fabric Port to join multiple fabrics. The port will
52 obtain an N_Port_ID on each fabric it joins. Each fabric will have its
61 expected. Once instantiated by one of the above methods, it will have a
63 The fc_host associated with the physical adapter will export the ability
64 to create vports. The transport will create the vport object within the
66 virtual port. Typically, the driver will create a new scsi_host instance
69 each will appear as a unique scsi_host with its own target and lun space.
75 discussion will concentrate on NPIV.
92 object corresponding to the physical adapter. The LLDD will allocate
99 a symbolic link to the vport object will be placed in the physical
[all …]
|
| /linux-6.15/Documentation/driver-api/surface_aggregator/clients/ |
| D | dtx.rst | 82 instructions/commands. In case the latch is unlocked, the led will flash
83 green. If the latch has been locked, the led will be solid red
90 If the EC does not receive any instructions in a given period, it will
93 - If the latch is unlocked, the EC will open the latch and the clipboard
98 - If the latch is locked, the EC will *not* open the latch, meaning the
105 - Execute ``SDTX_IOCTL_LATCH_REQUEST``. This will immediately abort the
106 detachment process. Furthermore, the EC will send a detach-request event,
110 - Execute ``SDTX_IOCTL_LATCH_CONFIRM``. This will cause the EC to open the
114 (``SDTX_EVENT_LATCH_STATUS``) will be sent once the latch has been opened
116 error or low battery, a latch-cancel event (``SDTX_EVENT_CANCEL``) will be
[all …]
|
| /linux-6.15/Documentation/trace/ |
| D | ring-buffer-design.rst | 44 - a pointer to the page that the reader will use next
47 - a pointer to the page that will be written to next
74 will stop writing to the buffer. This will lose most recent events.
77 before the consumer could free up anything, the producer will
78 overwrite the older data. This will lose the oldest events.
123 it will swap its page with the head_page. The old reader page will
124 become part of the ring buffer and the head_page will be removed.
125 The page after the inserted page (old reader_page) will become the
224 - the next page in the ring buffer that will be swapped
228 - the page where the next write will take place.
[all …]
|
| D | ftrace.rst | 53 option will do) the directory /sys/kernel/tracing will be created. To mount
72 the tracefs file system will be automatically mounted at:
76 All files located in the tracefs file system will be located in that
81 Any selected ftrace option will also create the tracefs file system.
82 The rest of the document will assume that you are in the ftrace directory
83 (cd /sys/kernel/tracing) and will only concentrate on the files within that
89 After mounting tracefs you will have access to the control and output files
117 kernel to disable writing to the ring buffer, which will
121 Note, the function and event trigger "traceoff" will also
131 (no tracer running, or tracing_on is zero), it will produce
[all …]
|
| /linux-6.15/Documentation/admin-guide/mm/ |
| D | transhuge.rst | 32 factor will affect all subsequent accesses to the memory for the whole
36 1) the TLB miss will run faster (especially with virtualization using
40 2) a single TLB entry will be mapping a much larger amount of virtual
60 and approporiately aligned. In this case, TLB misses will occur less
127 will inherit the top-level "enabled" value::
144 sizes, the kernel will select the most appropriate enabled size for a
165 means that an application requesting THP will stall on
172 means that an application will wake kswapd in the background
178 will enter direct reclaim and compaction like ``always``, but
180 other regions will wake kswapd in the background to reclaim
[all …]
|
| /linux-6.15/Documentation/core-api/ |
| D | circular-buffers.rst | 56 Typically, items will all be of the same unit size, but this isn't strictly
110 Each of these macros will nominally return a value between 0 and buffer_size-1,
114 they will return a lower bound as the producer controls the head index,
118 To the consumer it will show an upper bound as the producer may be busy
122 will return a lower bound as the consumer controls the tail index, but the
126 To the producer it will show an upper bound as the consumer may be busy
132 situation will merely be a guess, and may even be negative.
154 The producer will look something like this::
171 /* wake_up() will make sure that the head is committed before
178 This will instruct the CPU that the contents of the new item must be written
[all …]
|
| /linux-6.15/Documentation/process/ |
| D | stable-api-nonsense.rst | 20 will not break. I have old programs that were built on a pre 0.9something
54 kernel source interfaces. They both depend on each other, but we will
65 data structures will contain different alignment of structures, and
81 There is no way that binary drivers from one architecture will run
94 different options), so for even a single release you will need to create
97 Trust me, you will go insane over time if you try to support this kind
139 relatively little pain. If Linux had to ensure that it will preserve a
176 it will be fixed up by the person who did the kernel change in the first
183 - The quality of the driver will rise as the maintenance costs (to the
184 original developer) will decrease.
[all …]
|
| /linux-6.15/arch/sparc/include/asm/ |
| D | estate.h | 27 * 1) As the result of an instruction fetch, will generate instruction_access_error
28 * 2) As the result of a load etc. will generate data_access_error.
29 * 3) As the result of store merge completion, writeback, or copyout will
39 * reads resulting in a hardware corrected data or MTAG ECC error will generate an
42 * This same trap will also be generated when a hardware corrected ECC error results
46 /* In general, if the trap enable bits above are disabled the AFSR bits will still
47 * log the events even though the trap will not be generated by the processor.
|
| /linux-6.15/drivers/md/ |
| D | Kconfig | 35 <https://www.tldp.org/docs.html#howto>. There you will also learn
45 If you say Y here, then the kernel will try to autodetect raid
68 If you say Y here, then your multiple devices driver will be able to
69 use the so-called linear mode, i.e. it will combine the hard disk
73 will be called linear.
81 If you say Y here, then your multiple devices driver will be able to
82 use the so-called raid0 mode, i.e. it will combine the hard disk
84 up evenly, one chunk here and one chunk there. This will increase
89 <https://www.tldp.org/docs.html#howto>. There you will also
93 will be called raid0.
[all …]
|
| /linux-6.15/include/linux/ |
| D | key-type.h | 22 * This struct will be cleared and data and datalen will be set with the data
23 * and length parameters from the caller and quotalen will be set from
25 * key type, that will be called. Then the struct will be passed to the
28 * If the preparse() op is given, the free_preparse() op will be called to
82 * generating a proposed description and payload that will be handed to
93 * user's quota will hold the payload
115 * - the key's semaphore will be write-locked by the caller
126 * - permission checks will be done by the caller
127 * - the key's semaphore will be readlocked by the caller
147 * is known but will never block addition of a key)
|
| D | wait_bit.h | 63 * The process will wait on a waitqueue selected by hash from a shared
64 * pool. It will only be woken on a wake_up for the target bit, even
67 * Returned value will be zero if the bit was cleared in which case the
95 * Returned value will be zero if the bit was cleared in which case the
125 * Returned value will be zero if the bit was cleared in which case the
156 * Returned value will be zero if the bit was cleared in which case the
183 * Returned value will be zero if the bit was successfully set in which
234 * Returned value will be zero if the bit was successfully set in which
296 * The process will wait on a waitqueue selected by hash from a shared
297 * pool. It will only be woken on a wake_up for the given address.
[all …]
|
| /linux-6.15/drivers/of/unittest-data/ |
| D | overlay_bad_add_dup_prop.dtso | 9 * Thus the property "rpm_avail" in each fragment will
11 * This will result in an error and the overlay apply
12 * will fail.
18 * will occur if the overlay is removed. Since the overlay apply
19 * fails, the memory leak does actually occur, and kmemleak will
22 * memory leak and thus people who use kmemleak will not
|
| /linux-6.15/Documentation/ABI/removed/ |
| D | sysfs-selinux-checkreqprot | 21 will be removed no sooner than June 2021, at which point the kernel
22 will always cease using checkreqprot internally and will always
24 The checkreqprot selinuxfs node will remain for backward compatibility
25 but will discard writes of the "0" value and will reject writes of the
|
| /linux-6.15/Documentation/networking/device_drivers/hamradio/ |
| D | z8530drv.rst | 58 will read your /etc/z8530drv.conf.
236 run gencfg. It will generate the correct port addresses (I hope).
243 will print a skeleton z8530drv.conf for the OptoSCC to stdout.
310 installed will normally result in keying the transceiver until
323 This will create a network interface with the IP number 44.128.20.107
474 will just wait until the CTS signal is asserted. This
483 This is the probability that the transmitter will be keyed
499 The time the transmitter will remain keyed after the last
513 0: The interface will operate in CSMA mode (the normal
515 1: Fullduplex mode, i.e. the transmitter will be keyed at
[all …]
|
| /linux-6.15/Documentation/timers/ |
| D | no_hz.rst | 16 CONFIG_NO_HZ=n for older kernels). You normally will -not-
26 workloads, you will normally -not- want this option.
43 clock interrupts will normally be delivered any way because there
44 will frequently be multiple runnable tasks per CPU. In these cases,
45 attempting to turn off the scheduling clock interrupt will have no effect
53 periods, failing to omit scheduling-clock interrupts will result in
75 tickless". The remainder of this document will use "dyntick-idle mode".
119 delayed during a given iteration, all the other CPUs will be forced to
124 By default, no CPU will be an adaptive-ticks CPU. The "nohz_full="
141 the mode. Instead, the CPU will exit adaptive-ticks mode only if needed,
[all …]
|
| /linux-6.15/Documentation/userspace-api/ |
| D | ntsync.rst | 25 can be acquired without contention, or will wake up a waiting thread)
165 waiting on this semaphore will be woken and the semaphore's count
184 The mutex's count will be decremented by one. If decrementing the
186 unowned and signaled, and eligible threads waiting on it will be
194 Eligible threads will be woken, and auto-reset events will be
210 an auto-reset event which is pulsed, only one will be woken. If two
211 threads are waiting a manual-reset event which is pulsed, both will
212 be woken. However, in both cases, the event will be unsignaled
213 afterwards, and a simultaneous read operation will always report the
265 Eligible threads waiting on the mutex will be woken as appropriate
[all …]
|
| /linux-6.15/tools/testing/ktest/examples/include/ |
| D | defaults.conf | 11 # BOX here is defined as a variable that will be the name of the box
12 # itself. It is useful for calling scripts that will power cycle
49 # For accessing the machine, we will ssh to root@machine.
52 # Update this. The default here is ktest will ssh to the target box
59 # Each machine will have its own output build directory.
81 # and ktest will use that kernel to reboot into.
88 # The kernel build will use this option.
108 # seen in the console output, ktest will know the good kernel has
109 # finished rebooting and it will be able to continue the tests.
114 # something else, ktest will power cycle or reboot the target box
|
| /linux-6.15/arch/x86/kvm/ |
| D | Kconfig | 16 If you say N, all options in this submenu will be skipped and disabled.
57 virtualization extensions. You will need a fairly recent
58 processor equipped with virtualization extensions. You will also
65 will be called kvm.
91 software-protected VM will fail miserably.
103 will be called kvm-intel.
109 Checks that KVM's page table management code will not incorrectly
111 exceptions will be trapped by the hypervisor rather than injected
140 will be called kvm-amd.
214 Set the maximum number of vCPUs per KVM guest. Larger values will increase
|
| /linux-6.15/Documentation/admin-guide/cgroup-v1/ |
| D | devices.rst | 34 will remove the default 'a *:* rwm' entry. Doing::
38 will add the 'a *:* rwm' entry to the whitelist.
62 a cgroup's devices.deny file, all its children will have that entry removed
63 from their whitelist and all the locally set whitelist entries will be
82 "c 116:2 rwm" will be removed::
91 Notice that new whitelist entries will not be propagated::
120 Allowing or denying all by writing 'a' to devices.allow or devices.deny will
129 implementation. Removal or addition of exceptions that will reduce the access
130 to devices will be propagated down the hierarchy.
131 For every propagated exception, the effective rules will be re-evaluated based
|
| /linux-6.15/drivers/uio/ |
| D | Kconfig | 26 will be called uio_cif.
73 If you compile this as a module, it will be called uio_aec.
80 Automata GmbH. The userspace part of this driver will be
86 If you compile this as a module, it will be called uio_sercos3.
95 If you compile this as a module, it will be called uio_pci_generic.
106 will be called uio_netx.
121 This will add support for netX 51/52 devices connected via eLBC/GPCM.
139 If you compile this as a module, it will be called uio_mf624.
149 If you compile this as a module, it will be called uio_hv_generic.
166 If you compile this as a module, it will be called uio_dfl.
|
| /linux-6.15/Documentation/livepatch/ |
| D | callbacks.rst | 16 In most cases, (un)patch callbacks will need to be used in conjunction
63 callback will only be executed if its corresponding patch callback was
69 in-kernel vmlinux targets, this means that callbacks will always execute
71 callbacks will only execute if the target module is loaded. When a
72 module target is (un)loaded, its callbacks will execute only if the
80 pre-patch callback returns failure, the kernel's module loader will:
90 No post-patch, pre-unpatch, or post-unpatch callbacks will be executed
94 If a patch transition is reversed, no pre-unpatch handlers will be run
96 will only occur if their corresponding post-patch callback executed).
100 only the post-unpatch callback will be called.
|
| /linux-6.15/Documentation/filesystems/ |
| D | adfs.rst | 25 on a RISC OS Filecore filesystem, but will allow the data within files
35 uid=nnn All files in the partition will be owned by
37 gid=nnn All files in the partition will be in group
40 will be nnn. Default 0700.
42 will be nnn. Default 0077.
43 ftsuffix=n When ftsuffix=0, no file type suffix will be applied.
45 the RISC OS file type will be added. Default 0.
77 not a UnixExec filetype, then the permissions will be::
106 Mounting an ADFS disc with option ftsuffix=1 will cause appropriate file
108 ftsuffix option is zero or omitted, no file type suffixes will be added.
|
| /linux-6.15/Documentation/ABI/testing/ |
| D | sysfs-fs-ext4 | 14 The multiblock allocator will round up allocation
23 will search to find the best extent
30 will search to find the best extent
45 parameter will have their blocks allocated out of a
48 will have its blocks allocated out of its own unique
57 algorithm will pre-read into the buffer cache
97 The maximum number of megabytes the writeback code will
104 The maximum number of kilobytes which will be zeroed
107 that using a larger value will increase the
|
| /linux-6.15/drivers/net/ethernet/realtek/ |
| D | Kconfig | 14 kernel: saying N will just cause the configurator to skip all
15 the questions about Realtek devices. If you say Y, you will be asked for
32 will be called atp.
44 will be called 8139cp. This is recommended.
56 will be called 8139too. This is recommended.
85 instead of an internal one. Disabling this option will save some
114 will be called r8169. This is recommended.
130 Say Y here and it will be compiled and linked with the kernel
141 will be called rtase. This is recommended.
|
| /linux-6.15/arch/powerpc/platforms/ps3/ |
| D | Kconfig | 14 option will allow building otheros.bld, a kernel image suitable
31 kernel: saying N will just cause the configurator to skip all
48 system will have optimal runtime performance.
54 This option will enable kernel support to take advantage of the
77 general, all users will say Y or M.
88 general, all users will say Y or M.
123 In general, all users will say Y or M.
133 In general, all users will say Y or M.
145 In general, PS3 OtherOS users will say Y or M.
|
1...<<11121314151617181920>>...801