From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Andrew Morton <akpm@zip.com.au>, Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] buffermem_pages removal (5/5)
Date: Tue, 21 May 2002 14:54:12 -0700 [thread overview]
Message-ID: <332390000.1022018052@flay> (raw)
In-Reply-To: <3CEA9193.10F45174@zip.com.au>
> Yes, vaguely. Haven't thought about it a lot. I suspect the
> present kmap() infrastructure would collapse under the load,
> so surgery there would be needed first.
Hopefully I'll have that surgery completed this week, or early
next week, assuming the per-address space kmap is sufficient
for what you're looking at.
M.
next prev parent reply other threads:[~2002-05-21 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 13:10 [PATCH] buffermem_pages removal (5/5) Christoph Hellwig
2002-05-21 17:51 ` Andrew Morton
2002-05-21 17:53 ` Christoph Hellwig
2002-05-21 18:27 ` Andrew Morton
2002-05-21 21:54 ` Martin J. Bligh [this message]
2002-05-22 3:53 ` 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=332390000.1022018052@flay \
--to=martin.bligh@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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