linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Christian Smith <csmith@micromuse.com>
Cc: Daniel Phillips <phillips@bonn-fries.net>,
	Joseph A Knapka <jknapka@earthlink.net>,
	"Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
	linux-mm@kvack.org
Subject: Re: Why *not* rmap, anyway?
Date: Tue, 7 May 2002 16:23:34 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.44L.0205071620270.7447-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.33.0205071625570.1579-100000@erol>

On Tue, 7 May 2002, Christian Smith wrote:

> >> If not the Mach pmap layer, then surely another pmap-like
> >> layer would be beneficial.
> >
> >How about the one we already have?
>
> I don't like using a data structure as an 'API'. An API ideally gives
> you an interface to what you need to do, not how it's done. Sure, APIs
> can become obsolete, but function calls are MUCH easier to provide
> legacy support for than a large, complex data structure.

OK, this I can agree with.

I'd be interested in working with you towards a way of
hiding some of the data structure manipulation behind
a more abstract interface, kind of like what I've done
with the -rmap stuff ... nothing outside of rmap.c
knows about struct pte_chain and nothing should know.

If you could help find ways in which we can abstract
out manipulation of some more data structures I'd be
really happy to help implement and clean up stuff.

kind regards,

Rik
-- 
	http://www.linuxsymposium.org/2002/
"You're one of those condescending OLS attendants"
"Here's a nickle kid.  Go buy yourself a real t-shirt"

http://www.surriel.com/		http://distro.conectiva.com/

--
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/

  reply	other threads:[~2002-05-07 19:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21 22:27 Joseph A Knapka
2002-04-22  0:23 ` Martin J. Bligh
2002-04-22  2:13   ` Joseph A Knapka
2002-04-22  5:46     ` Martin J. Bligh
2002-04-23 22:40     ` Christian Smith
2002-04-24  0:46       ` Rik van Riel
2002-04-24 10:50         ` Christian Smith
2002-04-24 14:20           ` Rik van Riel
2002-04-24 14:37             ` Momchil Velikov
2002-04-24 14:52               ` Rik van Riel
2002-04-24 15:16                 ` Momchil Velikov
2002-04-24 18:31                   ` William Lee Irwin III
2002-04-25 15:19             ` Christian Smith
2002-05-05 19:04           ` Daniel Phillips
2002-05-07 18:37             ` Christian Smith
2002-05-07 19:23               ` Rik van Riel [this message]
2002-05-07 19:25                 ` William Lee Irwin III
2002-05-07 19:47                   ` Daniel Phillips
2002-05-07 19:50                     ` William Lee Irwin III
2002-05-07 23:02                       ` Daniel Phillips
2002-05-08  0:08                         ` William Lee Irwin III
2002-05-08  5:08                           ` Andrew Morton
2002-05-08  7:59                     ` Momchil Velikov
2002-05-08 14:33                       ` Daniel Phillips
2002-05-08 14:43                         ` Rik van Riel
2002-05-08 16:06                           ` Daniel Phillips
2002-05-08 16:10                             ` Rik van Riel
2002-05-07 19:49                   ` Rik van Riel
2002-05-07 19:53                     ` William Lee Irwin III
2002-05-07 19:43                 ` Daniel Phillips
2002-05-07 19:51                   ` Rik van Riel
2002-05-07 23:11                     ` Daniel Phillips
2002-05-07 21:21                   ` William Lee Irwin III
2002-05-07 23:15                     ` Daniel Phillips
2002-05-07 19:37               ` Daniel Phillips
2002-05-07 19:47                 ` William Lee Irwin III
2002-05-05 18:38         ` Daniel Phillips
2002-05-05 22:23           ` Rik van Riel

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.44L.0205071620270.7447-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=csmith@micromuse.com \
    --cc=jknapka@earthlink.net \
    --cc=linux-mm@kvack.org \
    --cc=phillips@bonn-fries.net \
    /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