mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Adam Litke <agl@us.ibm.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	Ken Chen <kenchen@google.com>, Bill Irwin <wli@holomorphy.com>
Subject: Re: [PATCH] Check for compound pages in set_page_dirty()
Date: Thu, 26 Jul 2007 18:59:21 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707261855290.13876@blonde.wat.veritas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707261042390.2335@schroedinger.engr.sgi.com>

On Thu, 26 Jul 2007, Christoph Lameter wrote:
> On Thu, 26 Jul 2007, Hugh Dickins wrote:
> 
> > I expect we could take that approach in the current kernel, yes
> > (though it would put those compound tests into the bio code that
> > Jens was preferring to remove).  But I think not if your variable
> > page_cache_size went in: imagine an mmap of the tail component page
> > of an order-1 page_cache_size page, and that pte only being dirtied:
> > wouldn't set_page_dirty on that page need to redirect to the head?
> 
> We would need to redirect all of the page state determinations and changes 
> to the head page anyways. So the memory.c code would have to deal with two 
> struct page pointers: One to the head where the state is kept and one to 
> the tail page that contains the actual chunk of data we are interested in. 
> The tail page pointer is only used for address determinations.
> 
> VM functions that manipulate the state of a page (like set_page_dirty) 
> could rely on only getting page heads.

Maybe.  Sounds ugly.  "would": so your patches remain just an RFC?

Hugh

  reply	other threads:[~2007-07-26 18:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 14:15 Jens Axboe
2007-07-18 15:40 ` Hugh Dickins
2007-07-18 18:24   ` Jens Axboe
2007-07-18 18:40     ` Jens Axboe
2007-07-18 20:35       ` Hugh Dickins
2007-07-19  6:29         ` Jens Axboe
2007-07-19  8:07           ` Jens Axboe
2007-07-19 17:35           ` Hugh Dickins
2007-07-20  0:34             ` William Lee Irwin III
2007-07-23 20:54             ` Christoph Lameter
2007-07-26 17:37               ` Hugh Dickins
2007-07-26 17:44                 ` Christoph Lameter
2007-07-26 17:59                   ` Hugh Dickins [this message]
2007-07-26 18:16                     ` Christoph Lameter
2007-07-18 18:45     ` Hugh Dickins
2007-07-18 18:49       ` Jens Axboe

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=Pine.LNX.4.64.0707261855290.13876@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=agl@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=jens.axboe@oracle.com \
    --cc=kenchen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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

all inboxes | Powered by JetHome®