From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>
Subject: VM deadlock avoidance
Date: Mon, 27 Nov 2006 15:06:25 +0100 [thread overview]
Message-ID: <1164636385.6588.28.camel@twins> (raw)
Hi Dave,
I have a new version of these patches; I'm still using SOCK_VMIO socket
tagging and skb->emergency marks, since I have not come up with another
approach that might work and my RFC to netdev has so far been ignored.
Other than this though, it changed quite a bit;
- I now use the regular allocation paths and cover all allocations
needed to process a skb (although the RX pool sizing might need more
variables)
- The emergency RX pool size is based on ip[46]frag_high_thresh and
ip[46]_rt_max_size so that fragment assembly and dst route cache
allocations cannot exhaust the memory. (more paths need analysis xfrm,
conntrack?)
- skb->emergency packets skip taps
- skb->emergency packets warn about and ignores NF_QUEUE targets
http://programming.kicks-ass.net/kernel-patches/vm_deadlock/v9/
The patches definitely need more work but would you agree with the
general direction I'm working in or would you suggest yet another
direction?
Kind regards,
Peter
next reply other threads:[~2006-11-27 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 14:06 Peter Zijlstra [this message]
2006-11-27 17:20 ` VM deadlock avoidance 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=1164636385.6588.28.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).