The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Larry Woodman <lwoodman@redhat.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: __alloc_pages() failures reported due to fragmentation
Date: Fri, 03 Nov 2006 07:39:44 -0500	[thread overview]
Message-ID: <454B3890.8070607@redhat.com> (raw)
In-Reply-To: <1162556514.14530.163.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:

>>--- linux-2.6.18.noarch/net/core/sock.c.orig
>>+++ linux-2.6.18.noarch/net/core/sock.c
>>@@ -1154,7 +1154,7 @@ static struct sk_buff *sock_alloc_send_p
>> 			goto failure;
>> 
>> 		if (atomic_read(&sk->sk_wmem_alloc) < sk->sk_sndbuf) {
>>-			skb = alloc_skb(header_len, sk->sk_allocation);
>>+			skb = alloc_skb(header_len, gfp_mask);
>> 			if (skb) {
>> 				int npages;
>> 				int i;
>>    
>>
>
>Hi,
>
>this is not actually right though... sk_allocation is very possible to
>have a restricting mask compared to the one passed in (say "no highmem"
>or even GFP_DMA) and you now discard this... probably better would be to
>calculate a set of "transient" flags that you then or into the
>sk_allocation mask at this time...
>
>Greetings,
>   Arjan van de Ven
>
>  
>
Hi Arjan.  Right but this just includes __GFP_REPEAT in the mask so we can
defrag in __alloc_pages and only if GFP_WAIT was passed in origionally.

Larry



  reply	other threads:[~2006-11-03 12:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 12:13 __alloc_pages() failures reported due to fragmentation Larry Woodman
2006-11-03 12:21 ` Arjan van de Ven
2006-11-03 12:39   ` Larry Woodman [this message]
2006-11-03 13:04     ` David Miller

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=454B3890.8070607@redhat.com \
    --to=lwoodman@redhat.com \
    --cc=arjan@infradead.org \
    --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