From: Pavel Machek <pavel@ucw.cz>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Ed L. Cashin" <ecashin@coraid.com>,
kernel list <linux-kernel@vger.kernel.org>,
ak@suse.de, Netdev list <netdev@vger.kernel.org>
Subject: Re: ATA over ethernet swapping
Date: Thu, 9 Aug 2007 12:11:05 +0200 [thread overview]
Message-ID: <20070809101105.GA7581@elf.ucw.cz> (raw)
In-Reply-To: <1185959909.12034.38.camel@twins>
Hi!
> I've been working on this for quite some time. And should post again
> soon. Please see the patches:
>
> http://programming.kicks-ass.net/kernel-patches/vm_deadlock/current/
>
> For now it requires one uses SLUB, I hope that SLAB will go away (will
> save me the trouble of adding support) and I guess I ought to do SLOB
> some time (if that does stay).
>
> You'd need the first 22 patches of that series, and then call
> sk_set_memalloc(sk) on the proper socket, and do some fiddling with the
> reconnect logic. See nfs-swapfile.patch for examples.
What do you use for testing? I set up ata over ethernet... swapping
over that should deadlock w/o your patches.
But I'm able to compile kernel (-j 10) on 128MB machine, and I tried
cat /dev/zero | grep foo to exhaust memory... and could not reproduce
the deadlock. Should I pingflood? Tweak down ammount of atomic memory
avaialable to make deadlocks easier to reproduce?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-08-09 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 13:58 ATA over ethernet swapping and obfuscated code Pavel Machek
2007-07-31 14:46 ` Sébastien Dugué
2007-07-31 15:03 ` Ed L. Cashin
2007-07-31 15:29 ` Pavel Machek
2007-07-31 16:21 ` Ed L. Cashin
2007-07-31 22:27 ` ATA over ethernet swapping Pavel Machek
2007-08-01 9:18 ` Peter Zijlstra
2007-08-09 10:11 ` Pavel Machek [this message]
2007-08-13 7:45 ` Peter Zijlstra
2007-08-21 7:42 ` Pavel Machek
2007-08-03 12:13 ` ATA over ethernet swapping and obfuscated code Torsten Kaiser
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=20070809101105.GA7581@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=ak@suse.de \
--cc=ecashin@coraid.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®