lkml.org 
[lkml]   [2001]   [Jul]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: __alloc_pages 4 order allocation failed
On Thu, 12 Jul 2001, Steffen Persvold wrote:

> Mike Galbraith wrote:
> >
> > On Wed, 11 Jul 2001, Ho Chak Hung wrote:
> >
> > > Hi,
> > > but there isn't any call in the module to allocate 4 order pages. There are only calls to allocate 0 order pages. alloc_pages(GFP_KERNEL, 0)is the only call to allocate page in the whole module.
> >
> > Then it's not your module :)
> >
> > Some driver may be asking for order 4, but settling for less when
> > that fails.
> >
> Why did this get worse on the 2.4 kernel ?. On 2.2 I always seemed to get my high order
> allocations and GFP_ATOMIC seldom failed when there was available memory.

If 2.2 manages to service high order allocations better than 2.4, I'd
say it must be due to dumb luck more than anything else. If you keep
most of your ram allocated (both 2.2 and 2.4 do), and don't do active
defragmentation (neither does), it's a roll of the dice whether you
have a contiguous chunk of ram to dole out or not.

wrt GFP_ATOMIC failing when memory is available, that doesn't happen
unless they are high order allocations. If you mean caches when you
say 'available', cache pages are not necessarily reclaimable at all,
much less instantly as would be required to service atomic allocations.

-Mike

-
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/

\
 
 \ /
  Last update: 2005-03-22 12:57    [W:0.039 / U:37.824 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site