From: Rik van Riel <riel@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: johnpol@2ka.mipt.ru, phillips@google.com, a.p.zijlstra@chello.nl,
indan@nul.nu, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [RFC][PATCH 0/4] VM deadlock prevention -v4
Date: Mon, 14 Aug 2006 10:22:40 -0400 [thread overview]
Message-ID: <44E08730.8080702@redhat.com> (raw)
In-Reply-To: <E1GCbux-0005CO-00@gondolin.me.apana.org.au>
Herbert Xu wrote:
> Rik van Riel <riel@redhat.com> wrote:
>> That should not be any problem, since skb's (including cowed ones)
>> are short lived anyway. Allocating a little bit more memory is
>> fine when we have a guarantee that the memory will be freed again
>> shortly.
>
> I'm not sure about the context the comment applies to, but skb's are
> not necessarily short-lived. For example, they could be queued for
> a few seconds for ARP/NDISC and even longer for IPsec SA resolution.
That's still below the threshold where it should cause problems
with the VM going OOM. Especially if there aren't too many of
these packets.
--
All Rights Reversed
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2006-08-14 14:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-12 14:14 Peter Zijlstra
2006-08-12 14:14 ` [RFC][PATCH 1/4] pfn_to_kaddr() for UML Peter Zijlstra
2006-08-12 14:14 ` [RFC][PATCH 2/4] SROG allocator Peter Zijlstra
2006-08-12 14:14 ` [RFC][PATCH 3/4] deadlock prevention core Peter Zijlstra
2006-08-12 14:41 ` Jeff Garzik
2006-08-12 15:06 ` rename *MEMALLOC flags (was: Re: [RFC][PATCH 3/4] deadlock prevention core) Peter Zijlstra
2006-08-12 15:28 ` Indan Zupancic
2006-08-12 15:34 ` Peter Zijlstra
2006-08-14 0:06 ` rename *MEMALLOC flags Daniel Phillips
2006-08-14 1:00 ` Paul Jackson
2006-08-14 3:42 ` Nick Piggin
2006-08-12 17:31 ` [RFC][PATCH 3/4] deadlock prevention core Indan Zupancic
2006-08-12 17:44 ` Peter Zijlstra
2006-08-12 17:54 ` Indan Zupancic
2006-08-12 18:08 ` Peter Zijlstra
2006-08-12 18:32 ` Indan Zupancic
2006-08-12 18:47 ` Peter Zijlstra
2006-08-12 19:45 ` Indan Zupancic
2006-08-12 14:14 ` [RFC][PATCH 4/4] deadlock prevention for NBD Peter Zijlstra
2006-08-24 14:43 ` Pavel Machek
2006-08-12 16:51 ` [RFC][PATCH 0/4] VM deadlock prevention -v4 Indan Zupancic
2006-08-12 17:33 ` Peter Zijlstra
2006-08-12 18:16 ` Indan Zupancic
2006-08-12 18:54 ` Peter Zijlstra
2006-08-12 20:05 ` Indan Zupancic
2006-08-14 0:42 ` Daniel Phillips
2006-08-14 5:20 ` Evgeniy Polyakov
2006-08-14 12:21 ` Rik van Riel
2006-08-14 12:51 ` Herbert Xu
2006-08-14 14:22 ` Rik van Riel [this message]
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=44E08730.8080702@redhat.com \
--to=riel@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=indan@nul.nu \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=phillips@google.com \
/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