All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eli Carter <eli.carter@inet.com>
To: george anzinger <george@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: standard queue implementation?
Date: Wed, 09 May 2001 14:06:10 -0500	[thread overview]
Message-ID: <3AF99522.C3DC59B@inet.com> (raw)
In-Reply-To: <3AF96062.19528A86@inet.com> <3AF98697.44437FEB@mvista.com>

george anzinger wrote:
> 
> Eli Carter wrote:
> >
> > All,
> >
> > I did a quick look in include/linux for a standard implementation of an
> > array-based circular queue, but I didn't see one.
> >
> > I was thinking something that could be declared, allocated, and then
> > used with an addq and a removeq.  A deallocator would also be good.
> >
> > Is there such a beast in the kernel?  If not, it seems that having
> > something like this would reduce the potential for bugs.
> >
> > Thoughts?
> >
> Are you possibly looking for include/linux/list.h ?
> 
> Routines to build and manager doubly linked circular lists.

I've seen that, but no.  I want a queue of pointers, and the queue
can/should be of fixed length.  (I don't want to deal with
allocating/deallocating nodes for this... I just need something simple.)

For now, I'll just write my own, but I may try submitting it as a
"kernel library" type thing later on.

Thanks,

Eli
-----------------------.   No wonder we didn't get this right first time
Eli Carter             |      through. It's not really all that horribly 
eli.carter(at)inet.com `- complicated, but the _details_ kill you. Linus

      reply	other threads:[~2001-05-09 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-09 15:21 standard queue implementation? Eli Carter
2001-05-09 18:04 ` george anzinger
2001-05-09 19:06   ` Eli Carter [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=3AF99522.C3DC59B@inet.com \
    --to=eli.carter@inet.com \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.