From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: Madper Xie <cxie@redhat.com>
Cc: Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Fengguang Wu <fengguang.wu@intel.com>,
David Cohen <david.a.cohen@linux.intel.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Damien Ramonda <damien.ramonda@intel.com>,
rientjes@google.com, Linus <torvalds@linux-foundation.org>,
nacc@linux.vnet.ibm.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V6 ] mm readahead: Fix readahead fail for memoryless cpu and limit readahead pages
Date: Tue, 18 Mar 2014 12:43:28 +0530 [thread overview]
Message-ID: <5327F218.1000506@linux.vnet.ibm.com> (raw)
In-Reply-To: <871ty1zig4.fsf@redhat.com>
On 03/17/2014 07:37 AM, Madper Xie wrote:
>
> Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com> writes:
>
>> On 02/18/2014 03:19 PM, Jan Kara wrote:
>>> On Tue 18-02-14 12:55:38, Raghavendra K T wrote:
> Hi. Just a concern. Will the performance reduce on some special storage
> backend? E.g. tape.
> The existent applications may using readahead for userspace I/O schedule
> to decrease seeking time.
I have not tested the patch on such systems yet unfortunately :(.
Sequential read with huge file has not suffered on disk based system,
but I think, I should be honest enough not to guess the effect on tape.
--
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:[~2014-03-18 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 7:25 [PATCH V6 ] mm readahead: Fix readahead fail for memoryless cpu and limit readahead pages Raghavendra K T
2014-02-18 9:49 ` Jan Kara
2014-02-18 12:04 ` Raghavendra K T
2014-02-18 12:04 ` Jan Kara
2014-03-17 2:07 ` Madper Xie
2014-03-18 7:13 ` Raghavendra K T [this message]
2014-02-18 22:23 ` David Rientjes
2014-02-18 22:38 ` Andrew Morton
2014-02-18 22:46 ` David Rientjes
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=5327F218.1000506@linux.vnet.ibm.com \
--to=raghavendra.kt@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cxie@redhat.com \
--cc=damien.ramonda@intel.com \
--cc=david.a.cohen@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nacc@linux.vnet.ibm.com \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).