From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Hirokazu Takahashi <taka@valinux.co.jp>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org
Subject: Re: [PATCH 2/4] Block I/O tracking
Date: Tue, 18 Mar 2008 20:55:01 +0900 [thread overview]
Message-ID: <20080318205501.59877972.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20080318.203422.45236787.taka@valinux.co.jp>
On Tue, 18 Mar 2008 20:34:22 +0900 (JST)
Hirokazu Takahashi <taka@valinux.co.jp> wrote:
>
> > And, blist seems to be just used for force_empty.
> > Do you really need this ? no alternative ?
>
> I selected this approach because it was the simplest way for the
> first implementation.
>
> I've been also thinking about what you pointed.
> If you don't mind taking a long time to remove a bio cgroup, it will be
> the easiest way that you can scan all pages to find the pages which
> belong to the cgroup and delete them. It may be enough since you may
> say it will rarely happen. But it might cause some trouble on machines
> with huge memory.
>
Hmm, force_empty itself is necessary ?
Thanks,
-Kame
--
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>
next prev parent reply other threads:[~2008-03-18 11:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 9:22 [PATCH O/4] " Hirokazu Takahashi
2008-03-18 9:25 ` [PATCH 1/4] " Hirokazu Takahashi
2008-03-18 10:25 ` KAMEZAWA Hiroyuki
2008-03-18 9:29 ` [PATCH 2/4] " Hirokazu Takahashi
2008-03-18 10:22 ` KAMEZAWA Hiroyuki
2008-03-18 11:34 ` Hirokazu Takahashi
2008-03-18 11:55 ` KAMEZAWA Hiroyuki [this message]
2008-03-18 12:15 ` Hirokazu Takahashi
2008-03-18 9:30 ` [PATCH 3/4] " Hirokazu Takahashi
2008-03-18 9:31 ` [PATCH 4/4] " Hirokazu Takahashi
2008-03-18 10:16 ` [PATCH O/4] " KAMEZAWA Hiroyuki
2008-03-19 3:59 ` Hirokazu Takahashi
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=20080318205501.59877972.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=taka@valinux.co.jp \
/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