linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Loke, Chetan" <Chetan.Loke@netscout.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Steven Whitehouse <swhiteho@redhat.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
	Wu Fengguang <fengguang.wu@gmail.com>, Jan Kara <jack@suse.cz>,
	Jeff Moyer <jmoyer@redhat.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	linux-scsi@vger.kernel.org, Mike Snitzer <snitzer@redhat.com>,
	neilb@suse.de, Christoph Hellwig <hch@infradead.org>,
	dm-devel@redhat.com, Boaz Harrosh <bharrosh@panasas.com>,
	linux-fsdevel@vger.kernel.org, lsf-pc@lists.linux-foundation.org,
	Chris Mason <chris.mason@oracle.com>,
	"Darrick J.Wong" <djwong@us.ibm.com>,
	linux-mm@kvack.org
Subject: RE: [Lsf-pc] [dm-devel]  [LSF/MM TOPIC] a few storage topics
Date: Wed, 25 Jan 2012 13:37:16 -0500	[thread overview]
Message-ID: <D3F292ADF945FB49B35E96C94C2061B915A63A50@nsmail.netscout.com> (raw)
In-Reply-To: <D3F292ADF945FB49B35E96C94C2061B915A63A30@nsmail.netscout.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 1444 bytes --]

> 
> > So there are two separate problems mentioned here.  The first is to
> > ensure that readahead (RA) pages are treated as more disposable than
> > accessed pages under memory pressure and then to derive a statistic for
> > futile RA (those pages that were read in but never accessed).
> >
> > The first sounds really like its an LRU thing rather than adding yet
> > another page flag.  We need a position in the LRU list for never
> > accessed ... that way they're first to be evicted as memory pressure
> > rises.
> >
> > The second is you can derive this futile readahead statistic from the
> > LRU position of unaccessed pages ... you could keep this globally.
> >
> > Now the problem: if you trash all unaccessed RA pages first, you end up
> > with the situation of say playing a movie under moderate memory
> > pressure that we do RA, then trash the RA page then have to re-read to display
> > to the user resulting in an undesirable uptick in read I/O.
> >


James - now that I'm thinking about it. I think the movie should be fine because when we calculate the read-hit from RA'd pages, the movie RA blocks will get a good hit-ratio and hence it's RA'd blocks won't be touched. But then we might need to track the hit-ratio at the RA-block(?) level.

Chetan

N‹§²æìr¸›zǧu©ž²Æ {\b­†éì¹»\x1c®&Þ–)îÆi¢žØ^n‡r¶‰šŽŠÝ¢j$½§$¢¸\x05¢¹¨­è§~Š'.)îÄÃ,yèm¶ŸÿÃ\f%Š{±šj+ƒñb‚^[nö¢®×¥yÊ&Š{^®w­r\x16«ë"œ&§iÖ¬Š	á¶Ú\x7fþËh¦Ø^™ë^­Æ¿\x0e‰ízf¢•¨ky

  reply	other threads:[~2012-01-25 18:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120124151504.GQ4387@shiny>
     [not found] ` <20120124165631.GA8941@infradead.org>
     [not found]   ` <186EA560-1720-4975-AC2F-8C72C4A777A9@dilger.ca>
     [not found]     ` <x49fwf5kmbl.fsf@segfault.boston.devel.redhat.com>
     [not found]       ` <20120124184054.GA23227@infradead.org>
     [not found]         ` <20120124190732.GH4387@shiny>
     [not found]           ` <x49vco0kj5l.fsf@segfault.boston.devel.redhat.com>
     [not found]             ` <20120124200932.GB20650@quack.suse.cz>
     [not found]               ` <x49pqe8kgej.fsf@segfault.boston.devel.redhat.com>
     [not found]                 ` <20120124203936.GC20650@quack.suse.cz>
     [not found]                   ` <20120125032932.GA7150@localhost>
     [not found]                     ` <F6F2DEB8-F096-4A3B-89E3-3A132033BC76@dilger.ca>
     [not found]                       ` <1327502034.2720.23.camel@menhir>
     [not found]                         ` <D3F292ADF945FB49B35E96C94C2061B915A638A6@nsmail.netscout.com>
     [not found]                           ` <1327509623.2720.52.camel@menhir>
2012-01-25 17:32                             ` James Bottomley
2012-01-25 18:28                               ` Loke, Chetan
2012-01-25 18:37                                 ` Loke, Chetan [this message]
2012-01-25 18:37                                 ` James Bottomley
2012-01-25 20:06                                   ` Chris Mason
2012-01-25 22:46                                     ` Andrea Arcangeli
2012-01-25 22:58                                       ` Jan Kara
2012-01-26  8:59                                       ` Boaz Harrosh
2012-01-26 16:40                                       ` Loke, Chetan
2012-01-26 17:00                                         ` Andreas Dilger
2012-01-26 17:16                                           ` Loke, Chetan
2012-02-03 12:37                                         ` Wu Fengguang
2012-01-26 22:38                                     ` Dave Chinner
2012-01-26 16:17                                   ` Loke, Chetan
2012-01-25 18:44                                 ` Boaz Harrosh

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=D3F292ADF945FB49B35E96C94C2061B915A63A50@nsmail.netscout.com \
    --to=chetan.loke@netscout.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=aarcange@redhat.com \
    --cc=adilger@dilger.ca \
    --cc=bharrosh@panasas.com \
    --cc=chris.mason@oracle.com \
    --cc=djwong@us.ibm.com \
    --cc=dm-devel@redhat.com \
    --cc=fengguang.wu@gmail.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=jmoyer@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=neilb@suse.de \
    --cc=snitzer@redhat.com \
    --cc=swhiteho@redhat.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