From: "Stephen C. Tweedie" <sct@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: lord@sgi.com, linux-kernel@vger.rutgers.edu, linux-mm@kvack.org,
sct@redhat.com, riel@conectiva.com.br
Subject: Re: kmap_kiobuf()
Date: Wed, 28 Jun 2000 19:07:03 +0100 [thread overview]
Message-ID: <20000628190703.F2392@redhat.com> (raw)
In-Reply-To: <13214.962208390@cygnus.co.uk>; from dwmw2@infradead.org on Wed, Jun 28, 2000 at 05:06:30PM +0100
Hi,
On Wed, Jun 28, 2000 at 05:06:30PM +0100, David Woodhouse wrote:
>
> MM is not exactly my field - I just know I want to be able to lock down a
> user's buffer and treat it as if it were in kernel-space, passing its
> address to functions which expect kernel buffers.
The pinning of user buffers is part of the reason we have kiobufs.
But why do you need to pass it to functions expecting kernel buffers?
--Stephen
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-06-28 18:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 15:54 kmap_kiobuf() lord
2000-06-28 16:06 ` kmap_kiobuf() David Woodhouse
2000-06-28 16:24 ` kmap_kiobuf() Benjamin C.R. LaHaise
2000-06-28 18:07 ` Stephen C. Tweedie [this message]
2000-06-28 18:45 ` kmap_kiobuf() David Woodhouse
2000-06-29 9:09 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-28 17:46 ` kmap_kiobuf() Stephen C. Tweedie
-- strict thread matches above, loose matches on Subject: below --
2000-06-28 20:16 kmap_kiobuf() lord
2000-06-28 21:22 ` kmap_kiobuf() Benjamin C.R. LaHaise
2000-06-29 9:34 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-29 13:45 ` kmap_kiobuf() Steve Lord
2000-06-28 16:52 kmap_kiobuf() lord
2000-06-28 18:06 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-28 19:06 ` kmap_kiobuf() Manfred Spraul
2000-06-28 21:05 ` kmap_kiobuf() Andi Kleen
2000-06-28 15:41 kmap_kiobuf() David Woodhouse
2000-06-28 17:44 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-29 10:52 ` kmap_kiobuf() Stephen C. Tweedie
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=20000628190703.F2392@redhat.com \
--to=sct@redhat.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=lord@sgi.com \
--cc=riel@conectiva.com.br \
/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