All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.68-mm2
Date: Wed, 23 Apr 2003 23:36:52 -0400	[thread overview]
Message-ID: <20030423233652.C9036@redhat.com> (raw)
In-Reply-To: <20030423144648.5ce68d11.akpm@digeo.com>; from akpm@digeo.com on Wed, Apr 23, 2003 at 02:46:48PM -0700

On Wed, Apr 23, 2003 at 02:46:48PM -0700, Andrew Morton wrote:
> Ingo-rmap seems a better solution to me.  It would be a fairly large change
> though - we'd have to hold the four atomic kmaps across an entire pte page
> in copy_page_range(), for example.  But it will then have good locality of
> reference between adjacent pages and may well be quicker than pte_chains.

Actually, Ingo's rmap style sounds very similar to what I first implemented 
in one of my stabs at rmap.  It has a nasty side effect of being worst case 
for cache organisation -- the sister page tends to map to the exact same 
cache line in some processors.  Whoops.  That said, I think that the rmap 
pte-chains can really stand a bit of optimization by means of discarding a 
couple of bits, as well as merging for adjacent pages, so I don't think 
the overhead is a lost cause yet.  And nobody has written the clone() patch 
for bash yet...

		-ben
-- 
Junk email?  <a href="mailto:aart@kvack.org">aart@kvack.org</a>

WARNING: multiple messages have this Message-ID (diff)
From: Benjamin LaHaise <bcrl@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.68-mm2
Date: Wed, 23 Apr 2003 23:36:52 -0400	[thread overview]
Message-ID: <20030423233652.C9036@redhat.com> (raw)
In-Reply-To: <20030423144648.5ce68d11.akpm@digeo.com>; from akpm@digeo.com on Wed, Apr 23, 2003 at 02:46:48PM -0700

On Wed, Apr 23, 2003 at 02:46:48PM -0700, Andrew Morton wrote:
> Ingo-rmap seems a better solution to me.  It would be a fairly large change
> though - we'd have to hold the four atomic kmaps across an entire pte page
> in copy_page_range(), for example.  But it will then have good locality of
> reference between adjacent pages and may well be quicker than pte_chains.

Actually, Ingo's rmap style sounds very similar to what I first implemented 
in one of my stabs at rmap.  It has a nasty side effect of being worst case 
for cache organisation -- the sister page tends to map to the exact same 
cache line in some processors.  Whoops.  That said, I think that the rmap 
pte-chains can really stand a bit of optimization by means of discarding a 
couple of bits, as well as merging for adjacent pages, so I don't think 
the overhead is a lost cause yet.  And nobody has written the clone() patch 
for bash yet...

		-ben
-- 
Junk email?  <a href="mailto:aart@kvack.org">aart@kvack.org</a>
--
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:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2003-04-24  3:24 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23  8:20 2.5.68-mm2 Andrew Morton
2003-04-23  8:20 ` 2.5.68-mm2 Andrew Morton
2003-04-23  9:59 ` 2.5.68-mm2 William Lee Irwin III
2003-04-23  9:59   ` 2.5.68-mm2 William Lee Irwin III
2003-04-23 16:50   ` 2.5.68-mm2 Robert Love
2003-04-23 16:50     ` 2.5.68-mm2 Robert Love
2003-04-23 16:57     ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 16:57       ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 17:11       ` 2.5.68-mm2 Robert Love
2003-04-23 17:11         ` 2.5.68-mm2 Robert Love
2003-04-24  9:14   ` 2.5.68-mm2 William Lee Irwin III
2003-04-24  9:14     ` 2.5.68-mm2 William Lee Irwin III
2003-04-23 12:08 ` 2.5.68-mm2 Ed Tomlinson
2003-04-23 12:37   ` 2.5.68-mm2 William Lee Irwin III
2003-04-23 14:25   ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 14:51 ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 14:51   ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 15:14   ` 2.5.68-mm2 Alex Tomas
2003-04-23 15:14     ` 2.5.68-mm2 Alex Tomas
2003-04-23 21:46   ` 2.5.68-mm2 Andrew Morton
2003-04-23 21:46     ` 2.5.68-mm2 Andrew Morton
2003-04-23 21:47     ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 21:47       ` 2.5.68-mm2 Martin J. Bligh
2003-04-24  3:39       ` 2.5.68-mm2 Benjamin LaHaise
2003-04-24  3:39         ` 2.5.68-mm2 Benjamin LaHaise
2003-04-24 21:13         ` 2.5.68-mm2 Martin J. Bligh
2003-04-24 21:13           ` 2.5.68-mm2 Martin J. Bligh
2003-04-24 23:13           ` objrmap (was 2.5.68-mm2) Martin J. Bligh
2003-04-24 23:13             ` Martin J. Bligh
2003-04-24  3:36     ` Benjamin LaHaise [this message]
2003-04-24  3:36       ` 2.5.68-mm2 Benjamin LaHaise
2003-04-24 20:24       ` 2.5.68-mm2 Bill Davidsen
2003-04-24 20:24         ` 2.5.68-mm2 Bill Davidsen
2003-04-24 20:33         ` 2.5.68-mm2 Benjamin LaHaise
2003-04-24 20:33           ` 2.5.68-mm2 Benjamin LaHaise
2003-04-25 17:56           ` 2.5.68-mm2 Bill Davidsen
2003-04-25 17:56             ` 2.5.68-mm2 Bill Davidsen
2003-04-25 18:20             ` 2.5.68-mm2 Randy.Dunlap
2003-04-25 18:20               ` 2.5.68-mm2 Randy.Dunlap
2003-04-25 18:27               ` 2.5.68-mm2 Robert Love
2003-04-25 18:27                 ` 2.5.68-mm2 Robert Love
2003-04-25 18:49                 ` 2.5.68-mm2 Martin J. Bligh
2003-04-25 18:49                   ` 2.5.68-mm2 Martin J. Bligh
2003-04-26 10:34                 ` 2.5.68-mm2 Bill Davidsen
2003-04-26 10:34                   ` 2.5.68-mm2 Bill Davidsen
2003-04-26 15:34                   ` 2.5.68-mm2 Martin J. Bligh
2003-04-26 15:34                     ` 2.5.68-mm2 Martin J. Bligh
2003-05-01  6:19 ` [BUG] 2.5.68-mm2 and list.h Alexander Hoogerhuis
2003-05-01  6:19   ` Alexander Hoogerhuis
2003-05-01  6:31   ` Andrew Morton
2003-05-01  6:31     ` Andrew Morton

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=20030423233652.C9036@redhat.com \
    --to=bcrl@redhat.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.