linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Ric Wheeler <rwheeler@redhat.com>,
	linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	lsf-pc@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes
Date: Fri, 24 Jan 2014 09:44:20 -0600 (CST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1401240941190.12665@nuc> (raw)
In-Reply-To: <20140124110928.GR4963@suse.de>

On Fri, 24 Jan 2014, Mel Gorman wrote:

> That'd be okish for 64-bit at least although it would show up as
> degraded performance in some cases when virtually contiguous buffers were
> used. Aside from the higher setup, access costs and teardown costs of a
> virtual contiguous buffer, the underlying storage would no longer gets
> a single buffer as part of the IO request. Would that not offset many of
> the advantages?

It would offset some of that. But the major benefit of large order page
cache was the reduction of the number of operations that the kernel has to
perform. A 64k page contains 16 4k pages. So there is only one kernel
operation required instead of 16. If the page is virtually allocated then
the higher level kernel functions still only operate on one page struct.
The lower levels (bio) then will have to deal with the virtuall mappings
and create a scatter gather list. This is some more overhead but not much.

Doing something like this will put more stress on the defragmentation
logic in the kernel. In general I think we need more contiguous physical
memory.

  reply	other threads:[~2014-01-24 15:44 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20  9:30 LSF/MM 2014 Call For Proposals Mel Gorman
2014-01-06 22:20 ` [LSF/MM TOPIC] [ATTEND] persistent memory progress, management of storage & file systems Ric Wheeler
2014-01-06 22:32   ` faibish, sorin
2014-01-07 19:44     ` Joel Becker
2014-01-21  7:00 ` LSF/MM 2014 Call For Proposals Michel Lespinasse
2014-01-22  3:04 ` [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes Ric Wheeler
2014-01-22  5:20   ` Joel Becker
2014-01-22  7:14     ` Hannes Reinecke
2014-01-22  9:34   ` [Lsf-pc] " Mel Gorman
2014-01-22 14:10     ` Ric Wheeler
2014-01-22 14:34       ` Mel Gorman
2014-01-22 14:58         ` Ric Wheeler
2014-01-22 15:19           ` Mel Gorman
2014-01-22 17:02             ` Chris Mason
2014-01-22 17:21               ` James Bottomley
2014-01-22 18:02                 ` Chris Mason
2014-01-22 18:13                   ` James Bottomley
2014-01-22 18:17                     ` Ric Wheeler
2014-01-22 18:35                       ` James Bottomley
2014-01-22 18:39                         ` Ric Wheeler
2014-01-22 19:30                           ` James Bottomley
2014-01-22 19:50                             ` Andrew Morton
2014-01-22 20:13                               ` Chris Mason
2014-01-23  2:46                                 ` David Lang
2014-01-23  5:21                                   ` Theodore Ts'o
2014-01-23  8:35                               ` Dave Chinner
2014-01-23 12:55                                 ` Theodore Ts'o
2014-01-23 19:49                                   ` Dave Chinner
2014-01-23 21:21                                   ` Joel Becker
2014-01-22 20:57                             ` Martin K. Petersen
2014-01-22 18:37                     ` Chris Mason
2014-01-22 18:40                       ` Ric Wheeler
2014-01-22 18:47                       ` James Bottomley
2014-01-23 21:27                         ` Joel Becker
2014-01-23 21:34                           ` Chris Mason
2014-01-23  8:27                     ` Dave Chinner
2014-01-23 15:47                       ` James Bottomley
2014-01-23 16:44                         ` Mel Gorman
2014-01-23 19:55                           ` James Bottomley
2014-01-24 10:57                             ` Mel Gorman
2014-01-30  4:52                               ` Matthew Wilcox
2014-01-30  6:01                                 ` Dave Chinner
2014-01-30 10:50                                 ` Mel Gorman
2014-01-23 20:34                           ` Dave Chinner
2014-01-23 20:54                         ` Christoph Lameter
2014-01-23  8:24                 ` Dave Chinner
2014-01-23 20:48             ` Christoph Lameter
2014-01-22 20:47           ` Martin K. Petersen
2014-01-23  8:21         ` Dave Chinner
2014-01-22 15:14     ` Chris Mason
2014-01-22 16:03       ` James Bottomley
2014-01-22 16:45         ` Ric Wheeler
2014-01-22 17:00           ` James Bottomley
2014-01-22 21:05             ` Jan Kara
2014-01-23 20:47     ` Christoph Lameter
2014-01-24 11:09       ` Mel Gorman
2014-01-24 15:44         ` Christoph Lameter [this message]
2014-01-22 15:54   ` James Bottomley
2014-03-14  9:02 ` Update on LSF/MM [was Re: LSF/MM 2014 Call For Proposals] James Bottomley

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=alpine.DEB.2.10.1401240941190.12665@nuc \
    --to=cl@linux.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=mgorman@suse.de \
    --cc=rwheeler@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;
as well as URLs for NNTP newsgroup(s).