Lines Matching refs:ring

17 tail - where new writes happen in the ring buffer.
19 head - where new reads happen in the ring buffer.
21 producer - the task that writes into the ring buffer (same as writer)
29 reader_page - A page outside the ring buffer used solely (for the most part)
52 The ring buffer can be used in either an overwrite mode or in
91 The ring buffer is made up of a list of pages held together by a linked list.
94 part of the ring buffer.
107 become part of the ring buffer and the head_page will be removed.
173 if what is in the ring buffer is less than what is held in a buffer page.
192 When the writer leaves the page, it simply goes into the ring buffer
193 since the reader page still points to the next location in the ring
200                 of the ring buffer (may be swapped in)
202   head page - the next page in the ring buffer that will be swapped
213 When data is written into the ring buffer, a position is reserved
214 in the ring buffer and passed back to the writer. When the writer
293 of the ring buffer: overwrite and produce/consumer).
314 part of the ring buffer, but the reader page is not. Whenever there
315 has been less than a full page that has been committed inside the ring buffer,
339 move back into the ring buffer.
341 The reader cannot swap a page into the ring buffer if the commit page
456 ring buffer. This means we only need to worry about a single reader,
459 When the reader tries to swap the page with the ring buffer, it
545 not part of the ring buffer. Traversing the ring buffer via the next pointers
546 will always stay in the ring buffer. Traversing the ring buffer via the
632 reader page? The commit page is not part of the ring buffer. The tail page