From: ali@internetdog.org (Ali Bahar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel list data structure
Date: Mon, 6 Jun 2011 09:59:14 +0800 [thread overview]
Message-ID: <20110606015914.GA15480@internetdog.org> (raw)
In-Reply-To: <BANLkTimLaxnDx99t-A7MCzjr2kbOcDo=gA@mail.gmail.com>
Hi Amirali,
> implemented a two-dimensioned list, using what I understood about kernel
> list. But as I debugged my code, it seems that my concept is wrong. Would
> anyone guide me how to implement a two-dimensioned list, or introduce me a
> manual to learn about it more?
I'm definitely on the newb end of things as far as kernel data
structures go. So getting another opinion would be prudent.
As for a manual, Wolfgang Mauerer's book, Professional Linux Kernel
Architecture, is an excellent resource. It does touch on double
linked-lists (LL), though I've only glanced at it.
> "noop_data" has a reference to start point of bundles list, called
> "writeQueue"
I don't think so. See below.
> struct bundle {
> struct list_head bundlesQueue;
> struct list_head reqsQueue;
What I see here is that you are putting such nodes on 2 LLs.
> struct noop_data {
> struct list_head readQueue;
> struct list_head writeQueue;
What I see here is that you are putting such nodes on 2 LLs, but
> struct bundle bun;
each node has a single node of the type 'struct bundle' ie a struct
which has
int bundleNumber;
int size;
...
int filled[8];
Likely, this is not what you want.
later,
ali
next prev parent reply other threads:[~2011-06-06 1:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 13:39 kernel list data structure Amirali Shambayati
2011-06-06 1:47 ` Jonathan Neuschäfer
2011-06-06 2:19 ` Ali Bahar
2011-06-06 4:00 ` Ali Bahar
2011-06-06 1:59 ` Ali Bahar [this message]
2011-06-06 5:35 ` Ali Bahar
2011-06-06 6:13 ` Amirali Shambayati
[not found] ` <BANLkTin1yNceh7d6d8AdTqDCiSmFxp976A@mail.gmail.com>
2011-06-06 6:31 ` Amirali Shambayati
2011-06-06 8:16 ` Amirali Shambayati
2011-06-06 14:31 ` Jonathan Neuschäfer
2011-06-07 1:51 ` Ali Bahar
2011-06-12 15:42 ` Amirali Shambayati
2011-06-13 10:57 ` Amirali Shambayati
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=20110606015914.GA15480@internetdog.org \
--to=ali@internetdog.org \
--cc=kernelnewbies@lists.kernelnewbies.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 NNTP newsgroup(s).