Date: Tue, 13 Jan 2009 14:42:08 -0800 (PST)
Message-Id: <20090113.144208.151478270.davem@davemloft.net>
To: Jesper.Nilsson@axis.com
Cc: tj@kernel.org, gregkh@suse.de, stern@rowland.harvard.edu,
       jens.axboe@oracle.com, hinko.kocevar@cetrtapot.si,
       linux-kernel@vger.kernel.org
Subject: Re: lib/klist.c: bit 0 in pointer can't be used as flag
From: David Miller <davem@davemloft.net>
In-Reply-To: <20090113221235.GD19262@axis.com>
References: <20090113151406.GC19262@axis.com>
	<20090113.131030.207355839.davem@davemloft.net>
	<20090113221235.GD19262@axis.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 741
Lines: 21

From: Jesper Nilsson <Jesper.Nilsson@axis.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/