Searched full:would (Results 1 – 25 of 876) sorted by relevance
12345678910>>...36
| /Documentation/w1/masters/ |
| D | ds2490.rst | 32 was added to the API. The name is just a suggestion. It would take
52 clear the entire bulk in buffer. It would be possible to read the
60 with a OHCI controller, ds2490 running in the guest would operate
64 would fail. qemu sets a 50ms timeout and the bulk in would timeout
65 even when the status shows data available. A bulk out write would
66 show a successful completion, but the ds2490 status register would
68 reattaching would clear the problem. usbmon output in the guest and
|
| /Documentation/networking/ |
| D | x25.rst | 18 implementation of LAPB. Therefore the LAPB modules would be called by
19 unintelligent X.25 card drivers and not by intelligent ones, this would
24 conform with the JNT "Pink Book", this would have a different interface to
25 the Packet Layer but there would be no confusion since the class of device
26 being served by the LLC would be completely separate from LAPB.
|
| D | snmp_counter.rst | 44 multicast packets, and would always be updated together with
137 would be increased even if the ICMP packet has an invalid type. The
139 IcmpOutMsgs would still be updated if the IP header is constructed by
207 IcmpMsgOutType8 would increase 1. And if kernel gets an ICMP Echo Reply
208 packet, IcmpMsgInType0 would increase 1.
215 IcmpInMsgs would be updated but none of IcmpMsgInType[N] would be updated.
225 counters would be updated. The receiving packet path use IcmpInErrors
227 is increased, IcmpInErrors would always be increased too.
263 packets would be delivered to the TCP layer, but the TCP layer will discard
266 counter would only increase 1.
[all …]
|
| D | representors.rst | 83 netdevice, while in hardware offload it would apply to packets transmitted by
133 access that the IP stack "sees" would then be configurable through tc rules;
136 networking entity, would not be appropriate for the representor and would
140 terminates IP traffic in software; in that case the DMA traffic would *not*
191 Similarly, since a TC mirred egress action targeting the representor would (in
204 would mean that all IPv4 packets from the VF are sent out the physical port, and
207 the VF would get two copies, as the packet reception on ``PORT_DEV`` would
210 On devices without separate port and uplink representors, ``PORT_DEV`` would
|
| /Documentation/filesystems/ |
| D | ocfs2-online-filecheck.rst | 13 necessary, since turning the filesystem read-only would affect other running
15 Then, a mount option (errors=continue) is introduced, which would return the
34 the offline fsck should/would be recommended.
43 by the inode number which caused the error. This inode number would be the
51 mounted. The file above would accept inode numbers. This could be used to
91 On receiving the inode, the filesystem would read the inode and the
92 file metadata. In case of errors, the filesystem would fix the errors
97 small linked list buffer which would contain the last (N) inodes
|
| D | directory-locking.rst | 193 we would have Dn a parent of D1, which is a parent of D2, which is
196 so they would all hold simultaneously at the deadlock time and
197 we would have a loop.
215 Dn and D1 would have to be among those, with Dn locked before D1.
219 it would be the first parent to be locked. Therefore at least one of the
221 of another - otherwise the operation would not have progressed past
224 It can't be a parent and its child; otherwise we would've had
226 would have to be a descendent of its child.
229 Otherwise the child of the parent in question would've been a descendent
240 rename is crucial - without it a deadlock would be possible. Indeed,
[all …]
|
| /Documentation/ |
| D | Kconfig | 20 written, it would be possible that some of those files would
21 have errors that would break them for being parsed by
|
| /Documentation/RCU/ |
| D | UP.rst | 26 from softirq, the list scan would find itself referencing a newly freed
47 its arguments would cause it to fail to make the fundamental guarantee
61 call_rcu() were to directly invoke the callback, the result would
65 In some cases, it would possible to restructure to code so that
70 the same critical section, then the code would need to create
82 or API changes would be required.
136 the process-context critical section. This would result in
150 simply immediately returned, it would prematurely signal the
151 end of the grace period, which would come as a nasty shock to
|
| D | lockdep-splat.rst | 78 which would permit us to invoke rcu_dereference_protected as follows::
83 With this change, there would be no lockdep-RCU splat emitted if this
85 or with the ->queue_lock held. In particular, this would have suppressed
104 read-side critical section, which again would have suppressed the
115 this change would also suppress the above lockdep-RCU splat.
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 27 would solve the second problem automatically.
36 One way would be to, similar to ``BPF_MAP_TYPE_PERF_EVENT_ARRAY``, make
38 enforce "same CPU only" rule. This would be more familiar interface compatible
39 with existing perf buffer use in BPF, but would fail if application needed more
42 Additionally, given the performance of BPF ringbuf, many use cases would just
44 approach would be an overkill.
48 with lookup/update/delete operations. This approach would add a lot of extra
50 would also add another concept that BPF developers would have to familiarize
51 themselves with, new syntax in libbpf, etc. But then would really provide no
60 ring buffer for all CPUs, it's as simple and straightforward, as would be with
[all …]
|
| /Documentation/scsi/ |
| D | lpfc.rst | 36 the LLDD would simply be queued for a short duration, allowing the device
38 to the system. If the driver did not hide these conditions, i/o would be
39 errored by the driver, the mid-layer would exhaust its retries, and the
40 device would be taken offline. Manual intervention would be required to
|
| D | megaraid.rst | 38 running "modprobe driver1" or "modprobe driver2" would automatically
50 both mptraid and megaraid would register with lsiioctl for each
51 adapter discovered, and lsiioctl would essentially be a switch,
|
| /Documentation/firmware-guide/acpi/ |
| D | osi.rst | 70 The ACPI BIOS flow would include an evaluation of _OS, and the AML
71 interpreter in the kernel would return to it a string identifying the OS:
83 of every possible version of the OS that would run on it, and needed to know
84 all the quirks of those OS's. Certainly it would make more sense
91 that anybody would install those old operating systems
104 eg. _OSI("3.0 Thermal Model") would return TRUE if the OS knows how
106 An old OS that doesn't know about those extensions would answer FALSE,
121 and its successors. To do otherwise would virtually guarantee breaking
156 which would increment, based on the version of the spec supported.
158 Unfortunately, _REV was also misused. eg. some BIOS would check
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 25 is also returned when the ioctl would need to wait for an event,
36 change something that would affect the stream, or would require
67 that this request would overcommit the usb bandwidth reserved for
|
| /Documentation/admin-guide/device-mapper/ |
| D | log-writes.rst | 31 The log would show the following:
36 cases where a power failure at a particular point in time would create an
42 Any REQ_OP_DISCARD requests are treated like WRITE requests. Otherwise we would
48 If we logged DISCARD when it completed, the replay would look like this:
82 we're fsck'ing something reasonable, you would do something like
89 This would allow you to replay the log up to the mkfs mark and
104 Say you want to test fsync on your file system. You would do something like
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-kim | 45 entry. This entry would be polled upon by the user-space
47 by the sysfs_notify. The value would be '1' when UART needs
48 to be opened/ldisc installed, and would be '0' when UART
|
| D | sysfs-bus-iio-mpu6050 | 8 is a 3x3 unitary matrix. A typical mounting matrix would look like
9 [0, 1, 0; 1, 0, 0; 0, 0, -1]. Using this information, it would be
|
| /Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 36 program would still need CAP_SETUID to do any kind of transition, but the
37 additional restrictions imposed by this LSM would mean it is a "safer" version
53 For candidate applications that would like to have restricted setid capabilities
54 as implemented in this LSM, an alternative option would be to simply take away
58 number of semantics around process spawning that would be affected by this, such
63 userspace would likely be less appealing to incorporate into existing projects
68 Another possible approach would be to run a given process tree in its own user
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 19 rule so that nice +19 level would be _exactly_ 1 jiffy. To better
39 So that if someone wanted to really renice tasks, +19 would give a much
40 bigger hit than the normal linear rule would do. (The solution of
47 millisec) rescheduling. (and would thus trash the cache, etc. Remember,
78 and another task with +2, the CPU split between the two tasks would
|
| /Documentation/locking/ |
| D | futex-requeue-pi.rst | 7 left without an owner if it has waiters; doing so would break the PI
20 implementation would wake the highest-priority waiter, and leave the
55 upon a successful futex_wait system call, the caller would return to
57 would be modified as follows::
93 acquire the rt_mutex as it would open a race window between the
|
| /Documentation/block/ |
| D | biovecs.rst | 11 More specifically, old code that needed to partially complete a bio would
13 ended up partway through a biovec, it would increment bv_offset and decrement
87 It used to be the case that submitting a partially completed bio would work
89 norm, not all drivers would respect bi_idx and those would break. Now,
98 where previously you would have used bi_idx you'd now use a bvec_iter,
|
| /Documentation/core-api/ |
| D | unaligned-memory-access.rst | 25 reading 4 bytes of data from address 0x10005 would be an unaligned memory
56 to architecture. It would be easy to write a whole document on the differences
94 starting at address 0x10000. With a basic level of understanding, it would
95 not be unreasonable to expect that accessing field2 would cause an unaligned
101 above case it would insert 2 bytes of padding in between field1 and field2.
116 where padding would otherwise be inserted, and hence reduce the overall
126 For a natural alignment scheme, the compiler would only have to add a single
172 Think about what would happen if addr1 was an odd address such as 0x10003.
218 To avoid the unaligned memory access, you would rewrite it as follows::
|
| /Documentation/security/ |
| D | ipe.rst | 16 of a locked-down system. This system would be born-secure, and have
19 specific data files would not be readable unless they passed integrity
20 policy. A mandatory access control system would be present, and
21 as a result, xattrs would have to be protected. This lead to a selection
22 of what would provide the integrity claims. At the time, there were two
44 policy would indicate what labels required integrity verification, which
45 presented an issue: EVM would protect the label, but if an attacker could
47 including the SELinux labels that would be used to determine whether the
95 1. Regression risk; many of these changes would result in
104 whose responsibility would be only the local integrity policy enforcement.
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | fw_search_path.rst | 16 only be up to 256 characters long. The kernel parameter passed would be:
25 You would echo into it your custom path and firmware requested will be searched
|
| /Documentation/userspace-api/media/dvb/ |
| D | dvbproperty.rst | 20 enough to group the structs that would be required for those new
21 standards. Also, extending it would break userspace.
69 The code that would that would do the above is show in
|
12345678910>>...36