From: Nick Piggin <npiggin@suse.de>
To: Len Brown <lenb@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Alexey Starikovskiy <aystarik@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-acpi@vger.kernel.org
Subject: Re: [patch][rfc] acpi: do not use kmem caches
Date: Mon, 1 Dec 2008 19:10:47 +0100 [thread overview]
Message-ID: <20081201181047.GK10790@wotan.suse.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0812011241080.3197@localhost.localdomain>
On Mon, Dec 01, 2008 at 12:53:04PM -0500, Len Brown wrote:
>
> > Or at least stop arguing and throwing bureaucratic stones in the way of
> > those wanting to sort out this mess.
>
> I think we all would be better served if there were more facts
> and fewer insults on this thread, can we do that please?
>
> I do not think the extra work we need to do for ACPICA changes
> are a significant hurdle here. We will do what is best for Linux --
> which is what we though we were doing when we changed ACPICA
> so Linux could use native caching in the first place.
>
> The only question that should be on the table here is how
> to make Linux be the best it can be.
If there is good reason to keep them around, I'm fine with that.
I think Pekka's suggestion of not doing unions but have better
typing in the code and then allocate the smaller types from
kmalloc sounds like a good idea.
If the individual kmem caches are here to stay, then the
kmem_cache_shrink call should go away. Either way we can delete
some code from slab.
The OS agnostic code that implements its own allocator is kind
of a hack -- I don't understand why you would turn on allocator
debugging and then circumvent it because you find it too slow.
But I will never maintain that so if it is compiled out for
Linux, then OK.
--
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>
next prev parent reply other threads:[~2008-12-01 18:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 8:31 Nick Piggin
2008-12-01 11:18 ` Pekka Enberg
2008-12-01 12:00 ` Nick Piggin
2008-12-01 13:12 ` Alexey Starikovskiy
2008-12-01 13:36 ` Nick Piggin
2008-12-01 14:14 ` Alexey Starikovskiy
2008-12-01 16:32 ` Nick Piggin
2008-12-01 17:18 ` Christoph Hellwig
2008-12-01 17:32 ` Alexey Starikovskiy
2008-12-01 13:37 ` Pekka Enberg
2008-12-01 14:02 ` Alexey Starikovskiy
2008-12-01 16:14 ` Nick Piggin
2008-12-01 16:45 ` Alexey Starikovskiy
2008-12-01 16:58 ` Nick Piggin
2008-12-01 17:20 ` Moore, Robert
2008-12-01 17:30 ` Andi Kleen
2008-12-01 17:32 ` Moore, Robert
2008-12-01 17:20 ` Christoph Hellwig
2008-12-01 17:49 ` Alexey Starikovskiy
2008-12-01 17:53 ` Len Brown
2008-12-01 18:10 ` Nick Piggin [this message]
2008-12-31 22:04 ` Len Brown
2009-01-05 4:14 ` Nick Piggin
2009-01-05 5:43 ` Skywing
2009-01-05 6:55 ` Nick Piggin
2008-12-01 14:32 ` Christoph Lameter
2008-12-01 14:48 ` Alexey Starikovskiy
2008-12-01 16:20 ` Nick Piggin
2008-12-01 17:04 ` Alexey Starikovskiy
2008-12-01 17:12 ` Nick Piggin
2008-12-01 17:25 ` Pekka Enberg
2008-12-01 17:32 ` Pekka Enberg
2008-12-01 17:36 ` Alexey Starikovskiy
2008-12-01 17:48 ` Pekka Enberg
2008-12-01 18:09 ` Christoph Lameter
2008-12-01 17:43 ` Alexey Starikovskiy
2008-12-01 17:31 ` Len Brown
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=20081201181047.GK10790@wotan.suse.de \
--to=npiggin@suse.de \
--cc=aystarik@gmail.com \
--cc=hch@infradead.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
/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