linux-kernel - Re: [PATCH] Use extents for recording what swap is allocated.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Oct 2006 09:03:33 +1000
From:	Nigel Cunningham <ncunningham@...uxmail.org>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Andrew Morton <akpm@...l.org>, "Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Use extents for recording what swap is allocated.

Hi.

On Tue, 2006-10-24 at 23:47 +0100, Christoph Hellwig wrote:
> On Wed, Oct 25, 2006 at 08:06:36AM +1000, Nigel Cunningham wrote:
> > IIRC, I avoided list.h because I only wanted a singly linked list (it
> > never gets traversed backwards). List.h looks to me like all doubly
> > linked lists. Do you know if there are any other singly linked list
> > implementations I could piggy-back?
> > 
> > That said, since there's normally not that many extents, I could switch
> > quite easily and it wouldn't normally waste much memory.
> 
> If the overhead doesn't matter for you (and I doubt it does) I'd say just
> use list.h.    Reusing existing code that doesn't need to be debugged and
> is idiomatically readable to everyone is very helpfull.

Ok.

Regards,

Nigel

-
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/