linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Christoph Lameter <clameter@sgi.com>,
	linux-mm@kvack.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: Slab: Remove kmem_cache_t
Date: Wed, 29 Nov 2006 17:41:18 +1100	[thread overview]
Message-ID: <456D2B8E.4060802@yahoo.com.au> (raw)
In-Reply-To: <20061128222409.cda8cd5e.akpm@osdl.org>

Andrew Morton wrote:
> On Wed, 29 Nov 2006 16:41:22 +1100
> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> 
> 
>>Andrew Morton wrote:
>>
>>>On Wed, 29 Nov 2006 15:42:44 +1100
>>>Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>>>
>>>
>>>
>>>>So what exactly is wrong with
>>>>a kmem_cache_t declaration in include files, then?
>>>
>>>
>>>a) it's a typedef and
>>>
>>>b) it's a typedef, and you cannot forward-declare typedefs.  We've hit this
>>>   a couple of times.  Header files need to include slab.h just to be able to do
>>>
>>>	extern kmem_cache_t *wozzle;
>>
>>So why doesn't
>>
>>   typedef struct kmem_cache kmem_cache_t;
>>   extern kmem_cache_t *wozzle;
>>
>>work?
>>
> 
> 
> Well, you'd just do
> 
> 	extern struct kmem_cache *wozzle;
> 
> because you "know" that struct kmem_cache == kmem_cache_t.  The compiler
> will swallow it all.
> 
> Do I need to explain how much that sucks?
> 

Well the only code that is doing this is presumably some slab internal
stuff. And that does "know" that struct kmem_cache == kmem_cache_t.
Actually, once struct kmem_cache gets moved into slab.h, I would be
interested to know what remaining forward dependencies are needed at
all. Christoph?

To be clear: this won't be some random driver or subsystem code (or
even anything outside of mm/slab.c, hopefully) that is doing this,
will it? If so then it sounds like just the kind of horrible design
that we should be trying to get away from (whether we're using
kmem_cache_t or struct kmem_cache as the caller-visible slab handle).

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-11-29  6:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29  2:49 Christoph Lameter
2006-11-29  3:06 ` Andrew Morton
2006-11-29  4:06 ` Nick Piggin
2006-11-29  3:32   ` Christoph Lameter
2006-11-29  4:42     ` Nick Piggin
2006-11-29  3:48       ` Nick Piggin
2006-11-29  4:06       ` Andrew Morton
2006-11-29  4:38         ` Linus Torvalds
2006-11-29  5:51           ` Nick Piggin
2006-11-29 15:48             ` Linus Torvalds
2006-11-30  1:40               ` Nick Piggin
2006-11-30  1:59                 ` Linus Torvalds
2006-11-30  2:14                   ` Nick Piggin
2006-11-30  2:37                     ` Linus Torvalds
2006-11-30  2:51                       ` Nick Piggin
2006-11-29  6:21           ` Nick Piggin
2006-11-29 16:11             ` Linus Torvalds
2006-11-29  5:41         ` Nick Piggin
2006-11-29  6:24           ` Andrew Morton
2006-11-29  6:41             ` Nick Piggin [this message]
2006-11-29  7:08               ` Andrew Morton
2006-11-29  7:23                 ` Nick Piggin
2006-11-29  7:41                   ` Andrew Morton
2006-11-29  8:04                     ` Nick Piggin
2006-11-29 16:23                       ` Linus Torvalds
2006-11-30  1:44                         ` Nick Piggin
2006-11-29 19:16               ` Christoph Lameter
2006-11-29  8:50 ` Peter Zijlstra
2006-11-29 19:27   ` Christoph Lameter

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=456D2B8E.4060802@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@osdl.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