From: Uma shankar <shankar.vk@gmail.com>
To: linux-mm@kvack.org
Subject: Ramzswap :swap-device write failure under low memory
Date: Thu, 8 Jul 2010 10:29:15 +0530 [thread overview]
Message-ID: <AANLkTikYX5U8eoMx5CDh00EVfVXDfO5eslYZ7DSB9zIe@mail.gmail.com> (raw)
Hi,
When using ramzswap, the internal allocator (xvMalloc) will try to
grow the pool,
when the compressed block will not fit in any of the existing free chunk.
This memory allocation can fail under low memory.
This will be informed to the kernel as a "device write" failure. The
page which was being written will
not be reclaimed, but the kernel will continue to try swap out of
other pages ( as kernel
thinks that swap has free space. )
Wont this lead to the reclaim code ( kswapd or the direct reclaim
path ) hogging the processor for some time
before OOM is finally announced ?
Has any one analysed this scenario ?
thanks
shankar
--
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>
reply other threads:[~2010-07-08 4:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AANLkTikYX5U8eoMx5CDh00EVfVXDfO5eslYZ7DSB9zIe@mail.gmail.com \
--to=shankar.vk@gmail.com \
--cc=linux-mm@kvack.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