Searched full:head (Results 1 – 25 of 138) sorted by relevance
123456
| /Documentation/translations/zh_CN/core-api/ |
| D | circular-buffers.rst | 53 (1) 'head'索引 - 生产者将元素插入缓冲区的位置。
144 unsigned long head = buffer->head;
148 if (CIRC_SPACE(head, tail, buffer->size) >= 1) {
150 struct item *item = buffer[head];
154 smp_store_release(buffer->head,
155 (head + 1) & (buffer->size - 1));
180 unsigned long head = smp_load_acquire(buffer->head);
183 if (CIRC_CNT(head, tail, buffer->size) >= 1) {
200 请注意，使用READ_ONCE()和smp_load_acquire()来读取反向（head）索引。这可以防止编译
201 器丢弃并重新加载其缓存值。如果您能确定反向（head）索引将仅使用一次，则这不是必须
|
| /Documentation/dev-tools/ |
| D | checkuapi.rst | 25 dirty changes, HEAD will be used.
77 Installing user-facing UAPI headers from HEAD... OK
78 Checking changes to UAPI headers between HEAD and dirty tree...
101 Installing user-facing UAPI headers from HEAD... OK
102 Checking changes to UAPI headers between HEAD and dirty tree...
103 ==== ABI differences detected in include/linux/bpf.h from HEAD -> dirty tree ====
125 Installing user-facing UAPI headers from HEAD... OK
126 Checking changes to UAPI headers between HEAD and dirty tree...
151 Installing user-facing UAPI headers from HEAD... OK
152 Checking changes to UAPI headers between HEAD and dirty tree...
[all …]
|
| /Documentation/core-api/ |
| D | circular-buffers.rst | 41 (1) A 'head' index - the point at which the producer inserts items into the
47 Typically when the tail pointer is equal to the head pointer, the buffer is
48 empty; and the buffer is full when the head pointer is one less than the tail
51 The head index is incremented when items are added, and the tail index when
52 items are removed. The tail index should never jump the head index, and both
114 they will return a lower bound as the producer controls the head index,
124 head index.
158 unsigned long head = buffer->head;
162 if (CIRC_SPACE(head, tail, buffer->size) >= 1) {
164 struct item *item = buffer[head];
[all …]
|
| /Documentation/locking/ |
| D | robust-futex-ABI.rst | 40 sys_set_robust_list(struct robust_list_head __user *head, size_t len);
42 The pointer 'head' points to a structure in the threads address space
45 its own thread private 'head'.
55 The first word in the memory structure at 'head' contains a
58 to itself, 'head'. The last 'lock entry' points back to the 'head'.
73 Each 'lock entry' on the single linked list starting at 'head' consists
75 'head' if there are no more entries. In addition, nearby to each 'lock
94 anticipates using robust_futexes, the kernel stores the passed in 'head'
111 By keeping its locks linked this way, on a list starting with a 'head'
120 list 'head' is, and to walk the list on thread exit, handling locks
[all …]
|
| D | ww-mutex-design.rst | 130 struct list_head head;
150 list_for_each_entry (entry, list, head) {
166 list_for_each_entry_continue_reverse (entry, list, head)
193 list_for_each_entry (entry, list, head) {
198 list_for_each_entry_continue_reverse (entry2, list, head)
210 * Move buf to head of the list, this will point
214 list_del(&entry->head);
215 list_add(&entry->head, list);
229 list_for_each_entry (entry, list, head)
|
| /Documentation/trace/ |
| D | ring-buffer-design.rst | 24 head
117 the head page, and its previous pointer pointing to a page before
118 the head page.
126 new head page.
132 show the head page in the buffer, it is for demonstrating a swap
223 head page
321 head page
328 head page commit page |
336 There is a special case that the head page is after either the commit page
338 swapped with the reader page. This is because the head page is always
[all …]
|
| /Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra186-dc.yaml | 65 nvidia,head:
66 description: The number of the display controller head. This
68 video data from the given head.
83 - nvidia,head
|
| D | nvidia,tegra186-display.yaml | 165 nvidia,head = <0>;
184 nvidia,head = <1>;
203 nvidia,head = <2>;
252 nvidia,head = <0>;
270 nvidia,head = <1>;
288 nvidia,head = <2>;
306 nvidia,head = <3>;
|
| D | nvidia,tegra20-dc.yaml | 70 nvidia,head:
72 description: The number of the display controller head. This is used to setup the various
73 types of output to receive video data from the given head.
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 42 This filling and emptying is managed by three pointers, the "head"
62 The head pointer (somewhat mis-named) follows after the tail pointer.
63 When traffic is flowing, then the head pointer will be pointing at
68 is flowing RX traffic, everything in front of the head pointer should
70 RX traffic is flowing, then the head pointer can catch up to the tail
71 pointer, at which point the OS will notice that the head descr is
74 Thus, in an idle system, the GDACTDPA, tail and head pointers will
79 GDACTDPA, tail and head pointers. It will also summarize the contents
87 net eth1: Chain head is at 20
94 head and tail are pointing at 20, because it has not yet been emptied.
[all …]
|
| /Documentation/admin-guide/laptops/ |
| D | disk-shock-protection.rst | 29 implement a generic disk head parking interface in the Linux kernel.
46 no further disk head park request has been issued in the meantime,
51 value between 0 and 30000 by issuing a subsequent head park request
57 timeout specified for a recent head park request has not yet expired,
82 confusion and should be discussed here. When a head park request has
86 be affected too. The only exception is that a subsequent head unload
92 which means that a user-issued head parking request to one device may
98 fine from the occasional buffer under-run incurred by a head park
147 This implementation of disk head parking has been inspired by a patch
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-xfs | 6 The log sequence number (LSN) of the current head of the
23 The current state of the log reserve grant head. It
33 The current state of the log write grant head. It
|
| /Documentation/mm/ |
| D | transhuge.rst | 38 head or tail pages as usual (exactly as they would do on
44 for the head page and not the tail page), it should be updated to jump
45 to check head page instead. Taking a reference on any head/tail page would
128 split_huge_page internally has to distribute the refcounts in the head
135 have a reference to the head page).
146 many references should be uncharged from the head page.
148 For head page get_page_unless_zero() will succeed and we don't mind. It's
149 clear where references should go after split: it will stay on the head page.
|
| /Documentation/devicetree/bindings/riscv/ |
| D | thead.yaml | 7 title: T-HEAD SoC-based boards
13 T-HEAD SoC-based boards
|
| /Documentation/RCU/ |
| D | rculist_nulls.rst | 66 for (pos = rcu_dereference((head)->first);
78 for (pos = rcu_dereference((head)->first);
109 * Please note that new inserts are done at the head of list,
164 head = &table[slot];
167 hlist_nulls_for_each_entry_rcu(obj, node, head, obj_node) {
204 * Please note that new inserts are done at the head of list,
|
| D | rcuref.rst | 73 call_rcu(&el->head, el_free); remove_element
77 call_rcu(&el->head, el_free);
111 ... call_rcu(&el->head, el_free);
|
| /Documentation/filesystems/ |
| D | erofs.rst | 323 extent is generated within the range (HEAD) or not (NONHEAD). Lclusters are now
333 (HEAD) (NONHEAD) (HEAD) (NONHEAD) .
347 For each HEAD lcluster, clusterofs is recorded to indicate where a new extent
350 distance to its HEAD lcluster and the next HEAD lcluster. A PLAIN lcluster is
351 also a HEAD lcluster except that its data is uncompressed. See the comments
360 | HEAD | NONHEAD | NONHEAD | ... | NONHEAD | HEAD | HEAD |
365 If another HEAD follows a HEAD lcluster, there is no room to record CBLKCNT,
|
| /Documentation/devicetree/bindings/clock/ |
| D | thead,th1520-clk-ap.yaml | 7 title: T-HEAD TH1520 AP sub-system clock controller
10 The T-HEAD TH1520 AP sub-system clock controller configures the
|
| /Documentation/fb/ |
| D | matroxfb.rst | 99 head, not even talking about second). Running XFree86 4.x accelerated mga
407 + secondary head shares videomemory with primary head. It is not problem
411 + due to hardware limitation, secondary head can use only 16 and 32bpp
413 + secondary head is not accelerated. There were bad problems with accelerated
414 XFree when secondary head used to use acceleration.
415 + secondary head always powerups in 640x480@60-32 videomode. You have to use
417 + secondary head always powerups in monitor mode. You have to use fbmatroxset
428 + secondary head shares videomemory with primary head. It is not problem
431 + due to hardware limitation, secondary head can use only 16 and 32bpp
433 + secondary head is not accelerated.
[all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-delayed-logging-design.rst | 228 grant head and the current log tail. That is, how much space can be
232 The first grant head is the "reserve" head. This tracks the byte count of the
239 The reserve grant head is used to accurately account for exact transaction
241 and need to write into the log. The reserve head is used to prevent new
242 transactions from taking new reservations when the head reaches the current
248 The other grant head is the "write" head. Unlike the reserve head, this grant
249 head contains an LSN and it tracks the physical space usage in the log. While
250 this might sound like it is accounting the same state as the reserve grant head
251 - and it mostly does track exactly the same location as the reserve grant head -
269 grant head does not track physical space - it only accounts for the amount of
[all …]
|
| /Documentation/translations/it_IT/doc-guide/ |
| D | sphinx.rst | 339 * - head col 1
340 - head col 2
341 - head col 3
342 - head col 4
361 * - head col 1
362 - head col 2
363 - head col 3
364 - head col 4
|
| /Documentation/process/ |
| D | backporting.rst | 161 between your currently checked-out branch (``HEAD``) and the parent of
164 git log HEAD..<commit>^ -- <path>
170 git log -L:'\<function\>':<path> HEAD..<commit>^
185 git log -G'regex' HEAD..<commit>^ -- <path>
258 <<<<<<< HEAD
270 ++<<<<<<<< HEAD
297 ``git diff HEAD`` (or ``git diff --ours``) which shows only the diff
301 $ git diff HEAD
303 +<<<<<<<< HEAD
321 <<<<<<< HEAD
[all …]
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | k3-ringacc.yaml | 22 with a new address which corresponds to the head or tail element of the ring
23 (head for reads, tail for writes).
|
| /Documentation/driver-api/serial/ |
| D | driver.rst | 51 port->state->xmit.head (circ_buf->head)
|
| /Documentation/doc-guide/ |
| D | sphinx.rst | 372 * - head col 1
373 - head col 2
374 - head col 3
375 - head col 4
394 * - head col 1
395 - head col 2
396 - head col 3
397 - head col 4
|
123456