From: pmkernel@gmail.com (piyush moghe)
To: kernelnewbies@lists.kernelnewbies.org
Subject: hlist_add_head
Date: Thu, 30 Jun 2011 14:48:01 +0530 [thread overview]
Message-ID: <BANLkTin9N_JedubojhX9+W4v0_B7rv5BCg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikb1ungKEJ_WoHOpMG+=-sHcFb5ag@mail.gmail.com>
On Thu, Jun 30, 2011 at 2:47 PM, piyush moghe <pmkernel@gmail.com> wrote:
> AFAIK hlist_add_head is a function to add a node at first position in
> collision chain at particular head ( hash bucket )
>
> For ex. whenever a new inode is allocated the hash value of that inode is
> calculated which acts as an index in inode_hashtable
> which subsequently provides and hash bucket ( head ) for that inode. Now
> this inode attached at the first position in collision chain for the
> calculated hash bucket pushing the current first inode to second position.
>
> For further clarification have a look at inode_add_to_lists() and
> __inode_add_to_lists() functions.
>
> Regards,
> Piyush
>
>
> On Tue, Jun 28, 2011 at 8:05 PM, luca ellero <lroluk@gmail.com> wrote:
>
>> Hi everybody,
>> can someone please explain what is the role of hlist_add_head (used in
>> in hash lists). Or maybe provide some links with good examples of its
>> use. I had a look at fs/dcache.c but frankly I can't understand it very
>> well.
>> Thanks in advance
>> Luca
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110630/14a130f7/attachment.html
prev parent reply other threads:[~2011-06-30 9:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 19:27 Linux module for causing a system hard lock-up limp
2011-06-08 20:12 ` Daniel Baluta
2011-06-08 22:24 ` limp
2011-06-08 22:53 ` Jeff Haran
2011-06-08 22:53 ` Greg KH
2011-06-09 4:28 ` Michael Blizek
2011-06-09 4:46 ` Michael Blizek
2011-06-09 7:06 ` Mulyadi Santosa
2011-06-14 20:23 ` limp
2011-06-14 21:36 ` João Eduardo Luís
2011-06-28 14:35 ` hlist_add_head luca ellero
[not found] ` <BANLkTikb1ungKEJ_WoHOpMG+=-sHcFb5ag@mail.gmail.com>
2011-06-30 9:18 ` piyush moghe [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=BANLkTin9N_JedubojhX9+W4v0_B7rv5BCg@mail.gmail.com \
--to=pmkernel@gmail.com \
--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).