From: Balachandar <bala1486@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: Doubt in linux kernel hlist implementation
Date: Thu, 17 Jun 2010 10:36:47 -0400 [thread overview]
Message-ID: <AANLkTilV6W3iAOBF9JBEZz8BlwDil0L0bxpkJmNTGK7N@mail.gmail.com> (raw)
Hi,
I am trying to understand Linux Kernel implementation of linked list
and hash table. A link to the implementation is here. I understood the
linked list implementation. But i am little confused of why double
pointers is being used in hlist (**pprev). Link for hlist is here. I
understand that hlist is used in implementation of hash table since
head of the list requires only one pointer and it saves space. Why
cant it be done using single pointer (just *prev like the linked
list)? Please help me.
Thanks,
Bala
--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2010-06-17 14:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AANLkTilV6W3iAOBF9JBEZz8BlwDil0L0bxpkJmNTGK7N@mail.gmail.com \
--to=bala1486@gmail.com \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).