From: Seth Huang <seth.hg@gmail.com>
To: Nick Piggin <npiggin@suse.de>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: OOM problem caused by fs
Date: Tue, 8 Jun 2010 01:34:17 +0800 [thread overview]
Message-ID: <AANLkTinKp3YO8h-pZqmEWhP1QHWawpVoVGW2ftc7R48v@mail.gmail.com> (raw)
In-Reply-To: <20100607095341.GM26335@laptop>
> Are you using set_page_dirty to dirty the pages?
Since part of our fs resembles nfs, we use
__set_page_dirty_nobuffers() for
address_space_operations->set_page_dirty, the same way nfs works.
> Are you sure you don't have a refcount leak?
One of my partners have already checked the page flags and reference
count. They seem to be all right.
Maybe we should check them again.
next prev parent reply other threads:[~2010-06-07 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 8:34 OOM problem caused by fs Seth Huang
2010-06-07 8:42 ` Boaz Harrosh
2010-06-07 9:53 ` Nick Piggin
2010-06-07 17:34 ` Seth Huang [this message]
2010-06-09 4:01 ` Tao Ma
2010-06-09 8:16 ` Seth Huang
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=AANLkTinKp3YO8h-pZqmEWhP1QHWawpVoVGW2ftc7R48v@mail.gmail.com \
--to=seth.hg@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@suse.de \
/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).