From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [v2] readahead02: fix read_ahead_kb file not found
Date: Tue, 13 Sep 2016 09:56:47 -0400 (EDT) [thread overview]
Message-ID: <1603573767.285723.1473775007201.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1526367732.41107.1473171720947.JavaMail.zimbra@redhat.com>
----- Original Message -----
> From: "Jan Stancek" <jstancek@redhat.com>
> To: "Naresh Kamboju" <naresh.kamboju@linaro.org>
> Cc: "graeme gregory" <graeme.gregory@linaro.org>, "milosz wasilewski" <milosz.wasilewski@linaro.org>,
> akpm@linux-foundation.org, "fengguang wu" <fengguang.wu@intel.com>, ltp@lists.linux.it
> Sent: Tuesday, 6 September, 2016 4:22:00 PM
> Subject: Re: [LTP] [v2] readahead02: fix read_ahead_kb file not found
>
>
>
>
>
> ----- Original Message -----
> > From: "Naresh Kamboju" <naresh.kamboju@linaro.org>
> > To: "Jan Stancek" <jstancek@redhat.com>
> > Cc: "chrubis" <chrubis@suse.cz>, ltp@lists.linux.it,
> > akpm@linux-foundation.org, "fengguang wu"
> > <fengguang.wu@intel.com>, "graeme gregory" <graeme.gregory@linaro.org>,
> > "milosz wasilewski"
> > <milosz.wasilewski@linaro.org>
> > Sent: Tuesday, 6 September, 2016 2:33:58 PM
> > Subject: Re: [LTP] [v2] readahead02: fix read_ahead_kb file not found
> >
> > Hi Jan,
> >
> > On 5 September 2016 at 13:06, Jan Stancek <jstancek@redhat.com> wrote:
> > >
> > >
> > > ----- Original Message -----
> > >> From: "naresh kamboju" <naresh.kamboju@linaro.org>
> > >> To: chrubis@suse.cz, ltp@lists.linux.it
> > >> Cc: akpm@linux-foundation.org, "fengguang wu" <fengguang.wu@intel.com>,
> > >> "graeme gregory" <graeme.gregory@linaro.org>,
> > >> "milosz wasilewski" <milosz.wasilewski@linaro.org>
> > >> Sent: Friday, 2 September, 2016 12:42:33 PM
> > >> Subject: [LTP] [v2] readahead02: fix read_ahead_kb file not found
> > >>
> > >> From: Naresh Kamboju <naresh.kamboju@linaro.org>
> > >>
> > >> Test case is looking for read_ahead_kb file on a partition device (8:2)
> > >> and
> > >> not on block device (8:0/8:16/8:32/8:48). The appropriate block device
> > >> that
> > >> holds the partition can be found at queue/read_ahead_kb entry.
Just fyi, there is a patch proposed to change this limit again:
https://lkml.org/lkml/2016/7/25/308
Regards,
Jan
prev parent reply other threads:[~2016-09-13 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 10:42 [LTP] [v2] readahead02: fix read_ahead_kb file not found naresh.kamboju
2016-09-05 7:36 ` Jan Stancek
2016-09-06 12:33 ` Naresh Kamboju
2016-09-06 14:22 ` Jan Stancek
2016-09-13 13:56 ` Jan Stancek [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=1603573767.285723.1473775007201.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.