From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Caspar Zhang <caspar@casparzhang.com>, Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] proc01: add option to limit max read bytes
Date: Thu, 23 Aug 2012 11:40:28 +0800 [thread overview]
Message-ID: <5035A62C.8060601@cn.fujitsu.com> (raw)
In-Reply-To: <5035A4CF.6000200@casparzhang.com>
On 08/23/2012 11:34 AM, Caspar Zhang wrote:
> On 07/31/2012 04:33 PM, Jan Stancek wrote:
>>
>> Add option -m to set upper limit of read megabytes from
>> single proc file. When this limit is reached testcase
>> will continue with next file.
>>
>> Reason for this new option is to allow running this testcase
>> as sanity test, that doesn't need go through full content of
>> files such as "pagemap" (which can take hours).
>>
>> Signed-off-by: Jan Stancek <jstancek@redhat.com>
> Reviewed-by: Caspar Zhang <caspar@casparzhang.com>
Pushed, thank you.
Wanlong Gao
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-08-23 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 8:33 [LTP] [PATCH] proc01: add option to limit max read bytes Jan Stancek
2010-02-16 2:27 ` chrubis
[not found] ` <1513655937.3221262.1348143318321.JavaMail.root@redhat.com>
2012-10-04 14:21 ` chrubis
2012-08-23 3:34 ` Caspar Zhang
2012-08-23 3:40 ` Wanlong Gao [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=5035A62C.8060601@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=caspar@casparzhang.com \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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