From: "Heinz, Michael" <mheinz@infiniconsys.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, <ignacio@openservices.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Implications of PG_locked and reference count in page structures....
Date: Wed, 15 Aug 2001 13:10:18 -0400 [thread overview]
Message-ID: <08628CA53C6CBA4ABAFB9E808A5214CB0C4C92@mercury.infiniconsys.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
Thanks for all the replies;
I am using the O'Reilly book - but I'm kind of stuck using the semantics
that the driver's original author used. The whole effort is so we can
experiment with some hardware rather than for final release, so we don't
want to spend too much effort reengineering anything we don't have to.
Heh. I missed the part in LDD that mentions kmalloc regions being
unpageable.
;->
--
"Oh, bother!" said the Borg. "We've assimilated Pooh!"
"Thanks for noticing." replied Eeyore.
mheinz@infiniconsys.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Heinz, Michael.vcf --]
[-- Type: text/x-vcard; name="Heinz, Michael.vcf", Size: 140 bytes --]
BEGIN:VCARD
VERSION:2.1
N:Heinz;Michael
FN:Heinz, Michael
EMAIL;PREF;INTERNET:mheinz@infiniconsys.com
REV:20010711T191535Z
END:VCARD
next reply other threads:[~2001-08-15 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 17:10 Heinz, Michael [this message]
[not found] <no.id>
2001-08-15 15:55 ` Implications of PG_locked and reference count in page structures Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 15:39 Michael Heinz
2001-08-15 16:04 ` Ignacio Vazquez-Abrams
2001-08-15 17:04 ` Daniel Phillips
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=08628CA53C6CBA4ABAFB9E808A5214CB0C4C92@mercury.infiniconsys.com \
--to=mheinz@infiniconsys.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ignacio@openservices.net \
--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;
as well as URLs for NNTP newsgroup(s).