All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Jes Sorensen <jes@wildopensource.com>
Cc: Andrew Morton <akpm@osdl.org>, Matthew Wilcox <matthew@wil.cx>,
	linux-ia64@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch -mm series] ia64 specific /dev/mem handlers
Date: Wed, 23 Feb 2005 00:48:44 +0000	[thread overview]
Message-ID: <1109119724.7277.25.camel@localhost> (raw)
In-Reply-To: <yq0650kl1gd.fsf@jaguar.mkp.net>

On Tue, 2005-02-22 at 16:38 -0500, Jes Sorensen wrote:
> >>>>> "Dave" = Dave Hansen <haveblue@us.ibm.com> writes:
> 
> Dave> I was talking with Nigel Cunningham about doing something a
> Dave> little different from the classic page flag bits when the number
> Dave> of users is restricted and performance isn't ultra-critical.
> Dave> Would something like this work for you, instead of using a real
> Dave> page->flags bit for PG_cached?
> 
> Just took a quick look at this and it looks a bit heavy for our
> use. We are only looking at a small number of pages. However I could
> imagine future cases where performance may be more critical.

If it's a quite small number (or range) of pages, perhaps a short
list_head list would suffice.  It would sure beat consuming a page flag.

-- Dave


WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Jes Sorensen <jes@wildopensource.com>
Cc: Andrew Morton <akpm@osdl.org>, Matthew Wilcox <matthew@wil.cx>,
	linux-ia64@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch -mm series] ia64 specific /dev/mem handlers
Date: Tue, 22 Feb 2005 16:48:44 -0800	[thread overview]
Message-ID: <1109119724.7277.25.camel@localhost> (raw)
In-Reply-To: <yq0650kl1gd.fsf@jaguar.mkp.net>

On Tue, 2005-02-22 at 16:38 -0500, Jes Sorensen wrote:
> >>>>> "Dave" == Dave Hansen <haveblue@us.ibm.com> writes:
> 
> Dave> I was talking with Nigel Cunningham about doing something a
> Dave> little different from the classic page flag bits when the number
> Dave> of users is restricted and performance isn't ultra-critical.
> Dave> Would something like this work for you, instead of using a real
> Dave> page->flags bit for PG_cached?
> 
> Just took a quick look at this and it looks a bit heavy for our
> use. We are only looking at a small number of pages. However I could
> imagine future cases where performance may be more critical.

If it's a quite small number (or range) of pages, perhaps a short
list_head list would suffice.  It would sure beat consuming a page flag.

-- Dave


  reply	other threads:[~2005-02-23  0:48 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22  9:52 [patch -mm series] ia64 specific /dev/mem handlers Jes Sorensen
2005-02-22  9:52 ` Jes Sorensen
2005-02-22 10:03 ` Andrew Morton
2005-02-22 10:03   ` Andrew Morton
2005-02-22 12:08   ` Andi Kleen
2005-02-22 12:08     ` Andi Kleen
2005-02-22 14:41   ` Jes Sorensen
2005-02-22 14:41     ` Jes Sorensen
2005-02-22 17:52     ` Matthew Wilcox
2005-02-22 19:25       ` Andrew Morton
2005-02-22 19:25         ` Andrew Morton
2005-02-22 19:35         ` Dave Hansen
2005-02-22 19:35           ` Dave Hansen
2005-02-22 21:38           ` Jes Sorensen
2005-02-22 21:38             ` Jes Sorensen
2005-02-23  0:48             ` Dave Hansen [this message]
2005-02-23  0:48               ` Dave Hansen
2005-02-22 21:34         ` Jes Sorensen
2005-02-22 21:34           ` Jes Sorensen
2005-02-22 22:39         ` Jes Sorensen
2005-02-22 22:39           ` Jes Sorensen
2005-02-22 23:34           ` Andrew Morton
2005-02-22 23:34             ` Andrew Morton
2005-02-23 10:01             ` Jes Sorensen
2005-02-23 10:01               ` Jes Sorensen
2005-02-23 22:34               ` Christoph Hellwig
2005-02-24 16:11                 ` Jes Sorensen
2005-02-24 16:11                   ` Jes Sorensen
2005-03-10  6:55                   ` Andrew Morton
2005-03-10  6:55                     ` Andrew Morton
2005-03-10 13:49                     ` Jes Sorensen
2005-03-10 13:49                       ` Jes Sorensen
2005-02-22 18:05 ` Luck, Tony
2005-02-22 18:05   ` Luck, Tony
2005-02-22 22:03 ` Arjan van de Ven
2005-02-22 22:03   ` Arjan van de Ven
2005-02-22 22:30   ` Jes Sorensen
2005-02-22 22:30     ` Jes Sorensen
2005-02-22 22:42     ` Arjan van de Ven
2005-02-22 22:42       ` Arjan van de Ven
2005-02-23  8:12       ` Jes Sorensen
2005-02-23  8:12         ` Jes Sorensen
2005-02-23  8:24         ` Arjan van de Ven
2005-02-23  8:24           ` Arjan van de Ven
2005-03-03 11:37 ` Andrew Morton
2005-03-03 11:37   ` Andrew Morton
2005-03-03 12:53   ` Jes Sorensen
2005-03-03 12:53     ` Jes Sorensen
2005-03-04 12:26     ` Jes Sorensen
2005-03-04 12:26       ` Jes Sorensen

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=1109119724.7277.25.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=jes@wildopensource.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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.