public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [rfc] generic allocator and mspec driver
Date: Sun, 13 Feb 2005 21:57:23 +0000	[thread overview]
Message-ID: <yq0ll9sp1h8.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <16897.9640.160896.31584@jaguar.mkp.net>

>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:

>>>>> On 03 Feb 2005 15:58:16 -0500, Jes Sorensen <jes@wildopensource.com> said:
Jes> I hear your concerns! However, at the same time, if something
Jes> within the kernel starts mocking with memory it doesn't own,
Jes> thats a bug.

David> I'm not convinced of that.  Jack already mentioned lcrash...

Mmmmm, I took a look at lcrash and I'll refrain from commenting on
it's method of operation here to avoid too much public swearing. Yuck!

Anyway, it seems that lcrash at least only accesses the memory using
read() and write()? which means it is relatively easy to using a
struct page flag to do uncached vs cached access on the fly. mmap on
the other hand would be a bit of a nightmare as it would require a
custom fault handler that would know when to go cached and when not
to.

How would you feel about using PG_arch_1 for this on ia64?

Cheers,
Jes

  parent reply	other threads:[~2005-02-13 21:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 19:10 [rfc] generic allocator and mspec driver Jes Sorensen
2005-02-02 19:46 ` Jesse Barnes
2005-02-02 23:33 ` Jack Steiner
2005-02-03  7:47 ` Jes Sorensen
2005-02-03  8:38 ` Jes Sorensen
2005-02-03 11:19 ` Robin Holt
2005-02-03 14:55 ` Jes Sorensen
2005-02-03 17:06 ` Jesse Barnes
2005-02-03 17:31 ` Dean Roe
2005-02-03 17:31 ` Robin Holt
2005-02-03 17:41 ` Jesse Barnes
2005-02-03 18:54 ` Jack Steiner
2005-02-03 19:39 ` David Mosberger
2005-02-03 20:58 ` Jes Sorensen
2005-02-03 21:40 ` Luck, Tony
2005-02-04  1:00 ` David Mosberger
2005-02-13 21:57 ` Jes Sorensen [this message]
2005-02-14 19:12 ` Luck, Tony
2005-02-14 19:17 ` David Mosberger
2005-02-15  8:43 ` Jes Sorensen
2005-02-15  8:44 ` Jes Sorensen
2005-02-15 17:35 ` Grant Grundler
2005-02-15 18:04 ` David Mosberger
2005-02-15 18:05 ` David Mosberger
2005-02-15 19:11 ` Robin Holt
2005-02-15 19:19 ` David Mosberger
2005-02-15 19:49 ` Robin Holt
2005-02-15 19:59 ` Jes Sorensen
2005-02-15 20:02 ` Jes Sorensen
2005-02-15 20:24 ` Robin Holt
2005-02-16  7:32 ` Jes Sorensen
2005-02-16 14:17 ` Jes Sorensen
2005-02-16 17:50 ` Luck, Tony
2005-02-16 18:18 ` Luck, Tony
2005-02-16 19:10 ` Jes Sorensen
2005-02-16 21:02 ` David Mosberger

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=yq0ll9sp1h8.fsf@jaguar.mkp.net \
    --to=jes@wildopensource.com \
    --cc=linux-ia64@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