From: Shuah Khan <shuahkh@osg.samsung.com>
To: naresh.kamboju@linaro.org, linux-kernel@vger.kernel.org
Cc: tyler.baker@linaro.org, milosz.wasilewski@linaro.org,
alexey.kodanev@oracle.com, Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH v3] selftests/zram: Adding zram tests
Date: Thu, 27 Aug 2015 16:12:07 -0600 [thread overview]
Message-ID: <55DF8B37.4060508@osg.samsung.com> (raw)
In-Reply-To: <55DF5288.4040405@osg.samsung.com>
On 08/27/2015 12:10 PM, Shuah Khan wrote:
> On 08/18/2015 01:01 AM, naresh.kamboju@linaro.org wrote:
>> From: Naresh Kamboju <naresh.kamboju@linaro.org>
>>
>> zram: Compressed RAM based block devices
>> ----------------------------------------
>> The zram module creates RAM based block devices named /dev/zram<id>
>> (<id> = 0, 1, ...). Pages written to these disks are compressed and stored
>> in memory itself. These disks allow very fast I/O and compression provides
>> good amounts of memory savings. Some of the usecases include /tmp storage,
>> use as swap disks, various caches under /var and maybe many more :)
>>
>> Statistics for individual zram devices are exported through sysfs nodes at
>> /sys/block/zram<id>/
>>
>> This patch is to validate the zram functionality. Test interacts with block
>> device /dev/zram<id> and sysfs nodes /sys/block/zram<id>/
>>
>
> Hi Naresh,
>
> This doesn't fail gracefully when a regular user runs it. Please add
> a check for root and make the test fail gracefully when a non-root
> user runs it.
>
> Please refer to tools/testing/selftests/efivarfs/efivarfs.sh
> for an example on how to check for root.
>
> I was getting ready to apply this to linux-kselftest next for 4.3
> and ran some sanity tests. If you get me new revision quickly
> I can get it into 4.3-rc1.
Hi Naresh,
The patch is now in linux-kselftest next. Please send a fix in for
the non-root case for me get it into 4.3-rc1 or rc2.
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
next prev parent reply other threads:[~2015-08-27 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 7:01 [PATCH v3] selftests/zram: Adding zram tests naresh.kamboju
2015-08-27 18:10 ` Shuah Khan
2015-08-27 22:12 ` Shuah Khan [this message]
2015-08-31 11:49 ` Naresh Kamboju
2015-08-31 4:07 ` Michael Ellerman
2015-08-31 12:19 ` Naresh Kamboju
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=55DF8B37.4060508@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=alexey.kodanev@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=milosz.wasilewski@linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=tyler.baker@linaro.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