From: Maxim Patlasov <mpatlasov@parallels.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, <riel@redhat.com>,
<jack@suse.cz>, <dev@parallels.com>, <miklos@szeredi.hu>,
<fuse-devel@lists.sourceforge.net>, <xemul@parallels.com>,
<linux-kernel@vger.kernel.org>, <jbottomley@parallels.com>,
<linux-mm@kvack.org>, <viro@zeniv.linux.org.uk>,
<linux-fsdevel@vger.kernel.org>, <devel@openvz.org>,
<mgorman@suse.de>
Subject: Re: [PATCH] mm: strictlimit feature -v4
Date: Thu, 22 Aug 2013 19:01:10 +0400 [thread overview]
Message-ID: <521627B6.6080603@parallels.com> (raw)
In-Reply-To: <20130822144121.GA620@localhost>
Hi,
08/22/2013 06:41 PM, Fengguang Wu пишет:
> Hi Maxim,
>
>>> I think I'll apply it to -mm for now to get a bit of testing, but would
>>> very much like it if Fengguang could find time to review the
>>> implementation, please.
>> Great! Fengguang, please...
> I'm so sorry for the delays!
>
> I'd like to test the patches out and take a look at its runtime
> behaviors. I've managed to setup general dd writeback tests. Do you
> happen to have some scripts that can specifically test out the fuse
> cases?
I used ordinary dd over fuse mount for testing. But fuse setup was
tricky. I'll send a writeup of my test environment to you tomorrow.
Thanks,
Maxim
--
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>
prev parent reply other threads:[~2013-08-22 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 13:56 [PATCH] mm: strictlimit feature -v4 Maxim Patlasov
2013-08-21 20:38 ` Andrew Morton
2013-08-22 10:15 ` Maxim Patlasov
2013-08-22 14:41 ` Fengguang Wu
2013-08-22 15:01 ` Maxim Patlasov [this message]
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=521627B6.6080603@parallels.com \
--to=mpatlasov@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=dev@parallels.com \
--cc=devel@openvz.org \
--cc=fengguang.wu@intel.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=jack@suse.cz \
--cc=jbottomley@parallels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=miklos@szeredi.hu \
--cc=riel@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.com \
/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).