public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] anobjrmap 1/6 objrmap
Date: Fri, 19 Mar 2004 06:38:08 -0800	[thread overview]
Message-ID: <20040319143808.GP2045@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0403182317050.16911-100000@localhost.localdomain>

On Thu, Mar 18, 2004 at 11:21:07PM +0000, Hugh Dickins wrote:
> First of six patches implementing full object-based rmap over 2.6.5-rc1,
> reviving my anonmm method to compare against Andrea's anon_vma method.
> I've not yet implemented Linus' early-COW solution to the mremap move
> issue, that will follow; handling of non-linear obj vmas also to follow.
> Sorry, not yet checked against wli's tree, he may have some fixes to it.

It would actually take serious rereading to verify that what issues I'd
fixed weren't ones I introduced myself. In that set of patches,
anobjrmap appeared alongside a page allocator rewrite, a top-down vma
allocation policy for i386, an arch/i386/mm/pgtable.c rewrite, wrapping
every modification to userspace ptes to track statistics wanted by
/proc/, highpmd, something that RCU'd inode->i_mmap{,_shared} missing
the needed smp_read_barrier_depends() calls, and using wrappers around
rwlocks to allow mapping->page_lock to be configured as an rwlock or
spinlock at compile-time thrown in for good measure, so there isn't
much of a way to rule out my own hacks. There was even experimental
junk at some point e.g. to remove files_lock in addition to a fair
number of other quetionable/buggy patches I dumped instead of debugging.

The story of that tree is too tortuous and sad to tell. I'll put up a
new tree with a substantially different emphasis, comprised of
completely different patches, when I have enough material to warrant it.


-- wli

  parent reply	other threads:[~2004-03-19 14:38 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18 23:21 [PATCH] anobjrmap 1/6 objrmap Hugh Dickins
2004-03-18 23:22 ` [PATCH] anobjrmap 2/6 linux/rmap.h Hugh Dickins
2004-03-18 23:23 ` [PATCH] anobjrmap 3/6 page->mapping Hugh Dickins
2004-03-18 23:25 ` [PATCH] anobjrmap 4/6 no pte_chains Hugh Dickins
2004-03-18 23:26 ` [PATCH] anobjrmap 5/6 anonmm Hugh Dickins
2004-03-19 16:15   ` Rik van Riel
2004-03-18 23:27 ` [PATCH] anobjrmap 6/6 cleanup Hugh Dickins
2004-03-19  2:42 ` [PATCH] anobjrmap 1/6 objrmap Andrea Arcangeli
2004-03-19  7:08   ` Hugh Dickins
2004-03-19 17:11     ` Martin J. Bligh
2004-03-20 12:30       ` Andrea Arcangeli
2004-03-20 14:03         ` William Lee Irwin III
2004-03-20 14:29           ` Andrea Arcangeli
2004-03-20 15:56         ` Martin J. Bligh
2004-03-20 16:19           ` Andrea Arcangeli
2004-03-20 16:40             ` Martin J. Bligh
2004-03-20 16:55               ` Andrea Arcangeli
2004-03-20 17:33                 ` Martin J. Bligh
2004-03-20 18:50                   ` Andrea Arcangeli
2004-03-21 16:30             ` Martin J. Bligh
2004-03-21 23:52               ` Andrea Arcangeli
2004-03-22 15:53                 ` Martin J. Bligh
2004-03-24  6:19                   ` Andrea Arcangeli
2004-03-24 15:56                     ` Martin J. Bligh
2004-03-24 16:21                       ` Andrea Arcangeli
2004-03-24 16:35                         ` Martin J. Bligh
2004-03-24 17:08                           ` Andrea Arcangeli
2004-03-24 20:00                             ` William Lee Irwin III
2004-03-24 20:01                         ` William Lee Irwin III
2004-03-24 20:17                           ` William Lee Irwin III
2004-03-20 12:46     ` Andrea Arcangeli
2004-03-19 14:38 ` William Lee Irwin III [this message]
2004-03-22 20:37 ` [PATCH] anobjrmap 7/6 mremap moves Hugh Dickins
2004-03-22 21:52   ` Rajesh Venkatasubramanian
2004-03-26 14:29 ` [PATCH] anobjrmap 8/6 unmap nonlinear Hugh Dickins
2004-03-26 14:54   ` Realtek 8139too drivers Linux Kernel

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=20040319143808.GP2045@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    /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