mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <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
Date: Tue, 13 Jan 2009 14:42:08 -0800 (PST)	[thread overview]
Message-ID: <20090113.144208.151478270.davem@davemloft.net> (raw)
In-Reply-To: <20090113221235.GD19262@axis.com>

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?

      parent reply	other threads:[~2009-01-13 22:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 15:14 Jesper Nilsson
2009-01-13 21:10 ` David Miller
2009-01-13 22:12   ` Jesper Nilsson
2009-01-13 22:40     ` KOSAKI Motohiro
2009-01-13 22:45       ` David Miller
2009-01-13 23:11         ` Bastien ROUCARIES
2009-01-14 10:19           ` Jesper Nilsson
2009-01-14 10:21             ` David Miller
2009-01-14 10:36               ` Jesper Nilsson
2009-01-14 10:45                 ` David Miller
2009-01-14 11:02                   ` Jesper Nilsson
2009-01-14 15:12                   ` Jesper Nilsson
2009-01-14 18:17                     ` Greg KH
2009-01-14 21:53                       ` Jesper Nilsson
2009-01-13 23:54         ` KOSAKI Motohiro
2009-01-13 23:59           ` Greg KH
2009-01-14 10:25             ` Jesper Nilsson
2009-01-14  0:33         ` Hugh Dickins
2009-01-14 10:18         ` Jesper Nilsson
2009-01-13 22:42     ` David Miller [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=20090113.144208.151478270.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Jesper.Nilsson@axis.com \
    --cc=gregkh@suse.de \
    --cc=hinko.kocevar@cetrtapot.si \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=tj@kernel.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

all inboxes | Powered by JetHome®