[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200804072256.FCJ21869.MJFFOVQtFOHSOL@I-love.SAKURA.ne.jp>
Date: Mon, 7 Apr 2008 22:56:47 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: dwalker@...sta.com
Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, takedakn@...data.co.jp,
haradats@...data.co.jp
Subject: Re: [TOMOYO #7 02/30] Internal functions prototypes for SAKURA andTOMOYO.
Daniel Walker wrote:
> > +/**
> > + * list1_entry - get the struct for this entry
> > + * @ptr: the &struct list1_head pointer.
> > + * @type: the type of the struct this is embedded in.
> > + * @member: the name of the list1_struct within the struct.
> > + */
> > +#define list1_entry(ptr, type, member) container_of(ptr, type,
> > member)
> > +
> > +/**
> > + * list1_for_each - iterate over a list
> > + * @pos: the &struct list1_head to use as a loop cursor.
> > + * @head: the head for your list.
> > + */
> > +#define list1_for_each(pos,
> > head) \
> > + for (pos = (head)->next; prefetch(pos->next), pos !=
> > (head); \
> > + pos = pos->next)
> > +
>
> These should go into include/linux/list.h .. It looks like you are
> duplicate at least some of what is already in there..
I see. I'll move it on next posting.
Although people advised me to use standard doubly linked list,
TOMOYO wants to use singly linked list because the elements are append only.
If TOMOYO is allowed to use singly linked list, it can make the source code read lock free.
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists