From: "Theodore Ts'o" <tytso@mit.edu>
To: David Howells <dhowells@redhat.com>
Cc: peterz@infradead.org, paulmck@linux.ibm.com,
linux@armlinux.org.uk, ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Consistent terminology for ring buffers
Date: Mon, 17 Jun 2019 09:45:55 -0400 [thread overview]
Message-ID: <20190617134555.GB4358@mit.edu> (raw)
In-Reply-To: <20265.1560522079@warthog.procyon.org.uk>
On Fri, Jun 14, 2019 at 03:21:19PM +0100, David Howells wrote:
>
> Can we settle on consistent terminology for ring buffers with regard to what
> we call the producer index and the consumer index?
"And all the people said, Amen!" :-)
> In linux/circ_buf.h and Documentation/core-api/circular-buffers.rst and
> various other places "head" is the index at which insertion occurs and "tail"
> is the index of the next object to be consumed.
That's certainly my preference; as Rusty said:
> To quote Russell: "head is where the food goes in, the tail is where the ..."
I was a bit confused by what you meant by this table?
> PRODUCER CONSUMER
> =============== ===============
> head tail
> tail head
> in out
> insert remove
> produce consume
Also, could you please make a submission of this proposal to the
kernel summit track here as well:
http://bit.ly/lpc19-submit
That will help us deal with scheduling. Thanks!!
- Ted
prev parent reply other threads:[~2019-06-17 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 14:21 [Ksummit-discuss] [TECH TOPIC] Consistent terminology for ring buffers David Howells
2019-06-17 13:45 ` Theodore Ts'o [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190617134555.GB4358@mit.edu \
--to=tytso@mit.edu \
--cc=dhowells@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux@armlinux.org.uk \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).