From: Martin Dalecki <dalecki@evision-ventures.com>
To: "Thomas 'Dent' Mirlacher" <dent@cosy.sbg.ac.at>
Cc: Linux-Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: comments on adding slist.h
Date: Sun, 09 Jun 2002 15:40:26 +0200 [thread overview]
Message-ID: <3D035ACA.2070309@evision-ventures.com> (raw)
In-Reply-To: <Pine.GSO.4.05.10206091405450.16324-100000@mausmaki.cosy.sbg.ac.at>
Thomas 'Dent' Mirlacher wrote:
> since we've already list.h, what about adding slist.h for
> single linked lists?
>
> single linked list are often used within the kernel,
> specifically slist_for_each() could be useful, since we can use
> prefetch() there. (slist_for_each could be used 42 times alone net/core)
>
> any comments, (like, single linked lists are so trivial, there is no
> need for a header file. or, the programmer has to take care of using
> prefetch() when traversing single linked lists ...) are welcome.
>
> thanks,
> tm
Just do it plese. It has been long overdue.
next prev parent reply other threads:[~2002-06-09 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 12:09 comments on adding slist.h Thomas 'Dent' Mirlacher
2002-06-09 13:40 ` Martin Dalecki [this message]
2002-06-09 21:04 ` William Lee Irwin III
2002-06-09 21:27 ` Thunder from the hill
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=3D035ACA.2070309@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=dent@cosy.sbg.ac.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox