From: Andrew Morton <akpm@osdl.org>
To: Stelian Pop <stelian@popies.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC, 2.6] a simple FIFO implementation
Date: Wed, 15 Sep 2004 15:30:13 -0700 [thread overview]
Message-ID: <20040915153013.32e797c8.akpm@osdl.org> (raw)
In-Reply-To: <20040913135253.GA3118@crusoe.alcove-fr>
Stelian Pop <stelian@popies.net> wrote:
>
> Hi all,
>
> Is there a reason there is no API implementing a simple in-kernel
> FIFO ? A linked list is a bit overkill...
>
> +struct kfifo {
> + unsigned int head;
> + unsigned int tail;
> + unsigned int size;
> + unsigned int len;
> + spinlock_t lock;
> + unsigned char *buffer;
> +};
A circular buffer implementation needs only head and tail indices. `size'
above appears to be redundant.
Implementation-wise, the head and tail indices should *not* be constrained
to be less than the size of the buffer. They should be allowed to wrap all
the way back to zero. This allows you to distinguish between the
completely-empty and completely-full states while using 100% of the storage.
> +static inline struct kfifo *kfifo_alloc(unsigned int size) {
This should not be inlined, and the caller should pass in the gfp_flags.
> +static inline void kfifo_reset(struct kfifo *fifo) {
uninline this.
> + unsigned long flags;
> +
> + spin_lock_irqsave(&fifo->lock, flags);
> +
> + fifo->head = fifo->tail = 0;
> + fifo->len = 0;
> +
> + spin_unlock_irqrestore(&fifo->lock, flags);
> +}
The caller should provide the locking. The spinlock should be removed.
Or maybe provide a separate higher-level API which does the locking for
you.
> +static inline unsigned int kfifo_put(struct kfifo *fifo,
> + unsigned char *buffer, unsigned int len) {
> + unsigned long flags;
> + unsigned int total, remaining;
> +
> + spin_lock_irqsave(&fifo->lock, flags);
> +
> + total = remaining = min(len, fifo->size - fifo->len);
> + while (remaining > 0) {
> + unsigned int l = min(remaining, fifo->size - fifo->tail);
> + memcpy(fifo->buffer + fifo->tail, buffer, l);
> + fifo->tail += l;
> + fifo->tail %= fifo->size;
> + fifo->len += l;
> + buffer += l;
> + remaining -= l;
> + }
> +
> + spin_unlock_irqrestore(&fifo->lock, flags);
> +
> + return total;
> +}
This is too big to inline.
> +static inline unsigned int kfifo_get(struct kfifo *fifo,
> + unsigned char *buffer, unsigned int len) {
> + unsigned long flags;
> + unsigned int total, remaining;
> +
> + spin_lock_irqsave(&fifo->lock, flags);
> +
> + total = remaining = min(len, fifo->len);
> + while (remaining > 0) {
> + unsigned int l = min(remaining, fifo->size - fifo->head);
> + memcpy(buffer, fifo->buffer + fifo->head, l);
> + fifo->head += l;
> + fifo->head %= fifo->size;
> + fifo->len -= l;
> + buffer += l;
> + remaining -= l;
> + }
> +
> + spin_unlock_irqrestore(&fifo->lock, flags);
> +
> + return total;
whitespace damage
> +}
Too big to inline.
> +/*
> + * kfifo_len - returns the number of bytes available in the FIFO
> + * @fifo: the fifo to be used.
> + */
> +static inline unsigned int kfifo_len(struct kfifo *fifo) {
> + unsigned long flags;
> + unsigned int result;
> +
> + spin_lock_irqsave(&fifo->lock, flags);
> +
> + result = fifo->len;
> +
> + spin_unlock_irqrestore(&fifo->lock, flags);
> +
> + return result;
> +}
And this.
next prev parent reply other threads:[~2004-09-15 22:30 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 13:52 Stelian Pop
2004-09-15 10:20 ` Stelian Pop
2004-09-15 11:10 ` Tonnerre
2004-09-15 11:25 ` Alan Cox
2004-09-15 13:27 ` Dmitry Torokhov
2004-09-15 14:21 ` Stelian Pop
2004-09-15 22:30 ` Andrew Morton [this message]
2004-09-16 6:43 ` Stelian Pop
2004-09-16 7:04 ` Andrew Morton
2004-09-16 10:45 ` Stelian Pop
2004-09-16 13:57 ` Paul Jackson
2004-09-16 14:09 ` Stelian Pop
2004-09-16 15:45 ` Paul Jackson
2004-09-16 15:59 ` Stelian Pop
2004-09-16 15:09 ` Buddy Lucas
2004-09-16 15:29 ` Stelian Pop
2004-09-16 15:51 ` Buddy Lucas
2004-09-16 15:52 ` Stelian Pop
2004-09-16 16:07 ` Buddy Lucas
2004-09-16 18:30 ` Stelian Pop
2004-09-16 22:52 ` Buddy Lucas
2004-09-16 17:00 ` Andrew Morton
2004-09-16 18:09 ` Stelian Pop
2004-09-17 0:18 ` Andrew Morton
2004-09-17 10:24 ` Stelian Pop
2004-09-17 11:28 ` Paul Jackson
2004-09-17 11:44 ` Hugh Dickins
2004-09-17 12:24 ` Stelian Pop
2004-09-17 12:37 ` Duncan Sands
2004-09-17 12:48 ` Stelian Pop
2004-09-17 13:00 ` Duncan Sands
2004-09-17 13:05 ` Stelian Pop
2004-09-17 13:16 ` Duncan Sands
2004-09-17 13:15 ` Andrea Arcangeli
2004-09-17 13:36 ` Stelian Pop
2004-09-17 13:41 ` Andrea Arcangeli
2004-09-17 14:00 ` Stelian Pop
2004-09-17 15:14 ` Andrea Arcangeli
2004-09-17 14:47 ` Paul Jackson
2004-09-17 12:52 ` James R Bruce
2004-09-17 15:48 ` Stelian Pop
2004-09-17 16:01 ` Andrea Arcangeli
2004-09-17 16:14 ` Hugh Dickins
2004-09-17 20:50 ` Stelian Pop
2004-09-17 21:28 ` Andrea Arcangeli
2004-09-17 21:54 ` Ryan Cumming
2004-09-17 22:00 ` Andrea Arcangeli
2004-09-17 22:14 ` Ryan Cumming
2004-09-17 22:35 ` Andrew Morton
2004-09-18 0:07 ` Ryan Cumming
2004-09-17 22:29 ` Ryan Cumming
2004-09-18 3:41 ` Kyle Moffett
2004-09-18 7:56 ` Ryan Cumming
2004-09-17 22:07 ` Andrew Morton
2004-09-20 15:14 ` Stelian Pop
2004-09-20 18:01 ` Sasha Khapyorsky
2004-09-20 18:22 ` Stelian Pop
2004-09-20 19:00 ` Richard B. Johnson
2004-09-16 15:57 ` Bill Davidsen
2004-09-17 10:25 ` Stelian Pop
[not found] <260353727@toto.iv>
2004-09-17 1:00 ` Peter Chubb
2004-09-17 5:45 ` Chris Friesen
2004-09-17 11:58 ` Anton Blanchard
2004-09-17 10:32 ` Stelian Pop
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=20040915153013.32e797c8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stelian@popies.net \
/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
Powered by JetHome