linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zlatko Calusic <Zlatko.Calusic@CARNet.hr>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Linux-MM List <linux-mm@kvack.org>,
	Linux Kernel List <linux-kernel@vger.rutgers.edu>,
	Rik van Riel <H.H.vanRiel@phys.uu.nl>,
	"David J. Fred" <djf@ic.net>
Subject: Re: unexpected paging during large file reads in 2.1.127
Date: 18 Nov 1998 23:50:07 +0100	[thread overview]
Message-ID: <87d86kwr8g.fsf@atlas.CARNet.hr> (raw)
In-Reply-To: "Stephen C. Tweedie"'s message of "Tue, 17 Nov 1998 12:00:37 GMT"


"Stephen C. Tweedie" <sct@redhat.com> writes:

> Hi,
> 
> On 17 Nov 1998 02:21:14 +0100, Zlatko Calusic <Zlatko.Calusic@CARNet.hr>
> said:
> 
> > "Stephen C. Tweedie" <sct@redhat.com> writes:
> 
> >> No, we don't.  We don't evict just-read-in data, because we mark such
> >> pages as PG_Referenced.  It takes two complete shrink_mmap() passes
> >> before we can evict such pages.
> 
> > I didn't find this in the source (in fact, add_to_page_cache clears
> > PG_referenced bit, if I understood source correctly). But, see below.
> 
> You didn't understand the source correctly. :)  There is an extra
> bracket you missed:
> 
> 	page->flags = (page->flags & ~((1 << PG_uptodate) | (1 << PG_error))) | (1 << PG_referenced);
> 
> We clear PG_uptodate and PG_error, but we _set_ PG_referenced.

Oops. My apologies. You're right, of course.

That makes one line in my patch superfluous.

Although I have some experience in LISP, it looks like I still have
trouble counting parentheses (LISP = Lost In Stupid Parentheses). :)

Still, a small comment above that line would be extremely helpful.

> 
> > I must agree entirely, because with small patch you can find below,
> > performance is very very good. Thanks to marking readahead pages as
> > referenced, I've been able to see exact behaviour that I wanted for a
> > long time. 
> 
> Excellent.  
> 

Pleasure is all mine. :)

I mean, bits from the patch are coming exclusively from you.

I'm really looking forward to their integration in the mainstream,
because performance improvement is so dramatic that I expect lots of
comments on the linux-kernel list telling that "latest 2.1.xxx is so
much faster".

Thanks for your good work!
-- 
Posted by Zlatko Calusic           E-mail: <Zlatko.Calusic@CARNet.hr>
---------------------------------------------------------------------
	"Luke... Luke... Use the MOUSE, Luke" - Obi Wan Gates
--
This is a majordomo managed list.  To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org

  reply	other threads:[~1998-11-18 22:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96.981112143712.20473B-100000@mirkwood.dummy.home>
1998-11-12 22:45 ` Zlatko Calusic
1998-11-16 19:59   ` Stephen C. Tweedie
1998-11-16 20:48     ` Rik van Riel
1998-11-16 23:05       ` Stephen C. Tweedie
1998-11-17  1:21         ` Zlatko Calusic
1998-11-17 12:00           ` Stephen C. Tweedie
1998-11-18 22:50             ` Zlatko Calusic [this message]
1998-11-17  6:42         ` Rik van Riel
1998-11-17 12:06           ` Stephen C. Tweedie
1998-11-17 20:25             ` Rik van Riel
1998-11-16 21:56     ` Zlatko Calusic
1998-11-12 23:18 ` Zlatko Calusic

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=87d86kwr8g.fsf@atlas.CARNet.hr \
    --to=zlatko.calusic@carnet.hr \
    --cc=H.H.vanRiel@phys.uu.nl \
    --cc=djf@ic.net \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=sct@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