Messages in this thread |  | | | Date | Thu, 10 Jun 2004 11:12:23 -0700 | | From | Andrew Morton <> | | Subject | Re: [PATCH] 2/5: Device-mapper: kcopyd |
| |
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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |