From: Erblichs <erblichs@earthlink.net>
To: Rik van Riel <riel@redhat.com>
Cc: Al Boldi <a1426z@gawab.com>, Chris Snook <csnook@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: How can we make page replacement smarter (was: swap-prefetch)
Date: Sat, 28 Jul 2007 23:40:02 -0700 [thread overview]
Message-ID: <46AC3642.6C60A0EF@earthlink.net> (raw)
In-Reply-To: <46AC1297.9030009@redhat.com>
Inline..
Mitchell Erblich
Rik van Riel wrote:
>
> Al Boldi wrote:
> > Chris Snook wrote:
>
> >> At best, reads can be read-ahead and cached, which is why
> >> sequential swap-in sucks less. On-demand reads are as expensive as I/O
> >> can get.
> >
> > Which means that it should be at least as fast as swap-out, even faster
> > because write to disk is usually slower than read on modern disks. But
> > linux currently shows a distinct 2x slowdown for sequential swap-in wrt
> > swap-out.
>
> That's because writes are faster than reads in moderate
> quantities.
Assuming that the write is not a partial write based
on first doing a read..
Yes, a COW FS minimes this condition (ex: ZFS)
However, since writes are mostly asynch in nature
most writers shouldn't care when the write is
actually commited, just that the data is stable
at some point in the future..
Thus, who would care (as long as we are not waiting
for the write to complete) if the write was slower.
IMO, it would make sense to ALMOST always generate
a certain amount of writable data before the write
is completed to attempt for the write to be as
"sequential" on the disk, so any later reads would
have minimal seeks..
>
> The disk caches writes, allowing the OS to write a whole
> bunch of data into the disk cache and the disk can optimize
> the IO a bit internally.
>
> The same optimization is not possible for reads.
>
> --
> Politics is the struggle between those who want to make their country
> the best in the world, and those who believe it already is. Each group
> calls the other unpatriotic.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
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:[~2007-07-29 6:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707272243.02336.a1426z@gawab.com>
2007-07-28 1:56 ` swap-prefetch: A smart way to make good use of idle resources (was: updatedb) Chris Snook
2007-07-28 4:17 ` How can we make page replacement smarter (was: swap-prefetch) Al Boldi
2007-07-28 7:27 ` Chris Snook
2007-07-28 11:11 ` Al Boldi
2007-07-29 4:07 ` Rik van Riel
2007-07-29 6:40 ` Erblichs [this message]
2007-07-29 1:46 ` How can we make page replacement smarter Rik van Riel
2007-07-29 13:09 ` Alan Cox
2007-07-29 15:01 ` Rik van Riel
2007-07-29 14:55 ` Al Boldi
2007-07-28 4:18 ` swap-prefetch: A smart way to make good use of idle resources (was: updatedb) Al Boldi
[not found] <fa.RQO1FPcnWSV7f0LbL9tuLuh/fYY@ifi.uio.no>
[not found] ` <fa.FI89MRq1q0M+6SmmYNPsXQv2gC8@ifi.uio.no>
[not found] ` <fa./S2LBynIjozRhHfPsYxB9mQDpKE@ifi.uio.no>
[not found] ` <fa.0CL7DLsw6U7akTkW79pdCM5NPRk@ifi.uio.no>
2007-07-28 16:32 ` How can we make page replacement smarter (was: swap-prefetch) Robert Hancock
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=46AC3642.6C60A0EF@earthlink.net \
--to=erblichs@earthlink.net \
--cc=a1426z@gawab.com \
--cc=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@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