linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, dgc@sgi.com, Mel Gorman <mel@skynet.ie>
Subject: Re: [patch 00/12] Slab defragmentation V3
Date: Fri, 8 Jun 2007 17:45:24 +0200	[thread overview]
Message-ID: <6bffcb0e0706080845y87b43b3of1920105caac2665@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706080826230.32210@schroedinger.engr.sgi.com>

On 08/06/07, Christoph Lameter <clameter@sgi.com> wrote:
> On Fri, 8 Jun 2007, Michal Piotrowski wrote:
>
> > Hi Christoph,
> >
> > On 07/06/07, clameter@sgi.com <clameter@sgi.com> wrote:
> > > Will show up shortly at
> > http://ftp.kernel.org/pub/linux/kernel/people/christoph/slab-defrag/
> >
> > I tried to apply this patchset, but without success. I tried
> > 2.6.22-rc4-mm2, 2.6.22-rc4, 2.6.22-rc4-git2, 2.6.22-rc3...
>
> Yeah its against 2.6.22-rc4-mm1 and 2.6.22-rc4-mm2 changes kernel/sysctl.c
> so that the defrag trigger patch fails. Sigh.
>
> I added kernel versions below slab-defrag so that you can find the correct
> version for your kernel.
>

It applies clean now, thanks. I'll test it later (I think I have found
an ancient bug, so now I build 2.6.17 ;))

Regards,
Michal

-- 
"Najbardziej brakowało mi twojego milczenia."
-- Andrzej Sapkowski "Coś więcej"

  reply	other threads:[~2007-06-08 15:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 21:55 clameter
2007-06-07 21:55 ` [patch 01/12] SLUB: Add support for kmem_cache_ops clameter
2007-06-07 21:55 ` [patch 02/12] SLUB: Slab defragmentation core functionality clameter
2007-06-07 21:55 ` [patch 03/12] SLUB: Extend slabinfo to support -D and -C options clameter
2007-06-07 21:55 ` [patch 04/12] SLUB: Slab defragmentation trigger clameter
2007-06-07 21:55 ` [patch 05/12] Generic inode defragmentation clameter
2007-06-07 21:55 ` [patch 06/12] ext2 ext3 ext4: support inode slab defragmentation clameter
2007-06-07 21:55 ` [patch 07/12] xfs: inode defragmentation support clameter
2007-06-07 21:55 ` [patch 08/12] procfs: " clameter
2007-06-07 21:55 ` [patch 09/12] reiserfs: " clameter
2007-06-07 21:55 ` [patch 10/12] sockets: " clameter
2007-06-07 21:55 ` [patch 11/12] Dentry defragmentation clameter
2007-06-07 21:55 ` [patch 12/12] SLUB: Support memory defrag through kmem_cache_vacate() clameter
2007-06-08  9:39 ` [patch 00/12] Slab defragmentation V3 Michal Piotrowski
2007-06-08 15:16   ` Christoph Lameter
2007-06-08 15:28   ` Christoph Lameter
2007-06-08 15:45     ` Michal Piotrowski [this message]
2007-06-08 18:02 ` Michal Piotrowski
2007-06-08 18:16   ` Christoph Lameter
2007-06-08 18:56     ` Michal Piotrowski
2007-06-08 19:08       ` Christoph Lameter
2007-06-08 19:32         ` Michal Piotrowski
2007-06-08 19:38           ` Christoph Lameter
2007-06-08 19:40         ` Christoph Lameter
2007-06-08 19:47           ` Michal Piotrowski
2007-06-08 20:48             ` Christoph Lameter
2007-06-08 21:17               ` Michal Piotrowski

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=6bffcb0e0706080845y87b43b3of1920105caac2665@mail.gmail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=dgc@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@skynet.ie \
    /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