public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Kevin Corry <kevcorry@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, agk@redhat.com
Subject: Re: [PATCH] 2/5: Device-mapper: kcopyd
Date: Thu, 10 Jun 2004 11:12:23 -0700	[thread overview]
Message-ID: <20040610111223.04a0c142.akpm@osdl.org> (raw)
In-Reply-To: <200406100816.18263.kevcorry@us.ibm.com>

Kevin Corry <kevcorry@us.ibm.com> wrote:
>
>  On Thursday 10 June 2004 6:18 am, Andrew Morton wrote:
>  > Alasdair G Kergon <agk@redhat.com> wrote:
>  > > kcopyd
>  > >
>  > > ...
>  > > +/* FIXME: this should scale with the number of pages */
>  > > +#define MIN_JOBS 512
>  >
>  > This pins at least 2MB of RAM up-front, even if devicemapper is not in use.
> 
>  Is that really the case?

No, sorry, I had CONFIG_DEBUG_PAGEALLOC turned on...

130k is still quite a lot.  Bear in mind that this memory is never used
unless the page allocation attept fails.  The mempool is there to prevent
OOM deadlocks and it is usually the case that a single mempool item is
sufficient for that.

  reply	other threads:[~2004-06-10 18:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 15:41 [PATCH] 2/5: Device-mapper: kcopyd Alasdair G Kergon
2004-06-02 16:15 ` Andreas Dilger
2004-06-02 16:50   ` Kevin Corry
2004-07-03  5:44     ` Daniel Phillips
2004-06-02 21:15   ` Alasdair G Kergon
2004-06-03  3:41 ` Andrew Morton
2004-06-03 13:28   ` Alasdair G Kergon
2004-06-10  6:18 ` Andrew Morton
2004-06-10  8:16   ` Kevin Corry
2004-06-10 18:12     ` Andrew Morton [this message]
2004-06-10 14:55   ` Alasdair G Kergon

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=20040610111223.04a0c142.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=agk@redhat.com \
    --cc=kevcorry@us.ibm.com \
    --cc=linux-kernel@vger.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