[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090113.144208.151478270.davem@davemloft.net>
Date: Tue, 13 Jan 2009 14:42:08 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: Jesper.Nilsson@...s.com
Cc: tj@...nel.org, gregkh@...e.de, stern@...land.harvard.edu,
jens.axboe@...cle.com, hinko.kocevar@...rtapot.si,
linux-kernel@...r.kernel.org
Subject: Re: lib/klist.c: bit 0 in pointer can't be used as flag
From: Jesper Nilsson <Jesper.Nilsson@...s.com>
Date: Tue, 13 Jan 2009 23:12:35 +0100
> Can you recall another place where this trick is used?
>
> It seems that rt_mutex uses the same trick (with the lowest 2bits)
> but AFAICT that's something we don't use on CRIS.
Sparsemem uses it.
The TRIE based routing tables uses it.
All of the IPV4/IPV6 socket hash tables use it as of 2.6.29-rc1.
You really can't avoid supporting this. Why doesn't kmalloc
return properly aligned objects on CRIS?
--
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