From: David Woodhouse <dwmw2@infradead.org>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: lord@sgi.com, linux-kernel@vger.rutgers.edu, linux-mm@kvack.org,
riel@conectiva.com.br
Subject: Re: kmap_kiobuf()
Date: Wed, 28 Jun 2000 19:45:57 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.21.0006281930220.987-100000@imladris.demon.co.uk> (raw)
In-Reply-To: <20000628190703.F2392@redhat.com>
On Wed, 28 Jun 2000, Stephen C. Tweedie wrote:
> 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?
So far I've encountered two places where I've wanted to do this.
First, in copying a packet from userspace to a PCI card, where I have to
have interrupts disabled locally (spin_lock_irq()).
Currently, it does:
lock_iobuf()
foreach(page)
kmap(page) (and store the address in an array)
spin_lock_irq()
foreach(page or part thereof)
memcpy_toio() (using the virtadr returned by kmap)
spin_unlock_irq()
foreach(page)
kunmap(page)
unlock_iobuf()
The memcpy_toio() has to be split into page-sized chunks, and because we
have to do the kmap from outside the spinlock, I have to keep an array of
virtual addresses.
If it's really that difficult to map them contiguously into VM, I suppose
it can stay the way it is - actually I can probably get away without the
array of virtual addresses by discarding the return value of kmap() and
using page_address() from within the spinlock, can't I?
Secondly, for the character device access to MTD devices. Almost all
access to MTD devices uses kernel-space buffers. I don't really want to
bloat _every_ MTD driver by making it conditionally user/kernel.
The only exception is the direct chardevice access, for which I'm
currently using bounce buffers, but would like to just lock down the pages
and pass a contiguously-mapped VM address instead.
Again, if it's really that much of a problem, I can work round it. It just
seemed like the ideal solution, that's all.
> For any moderately large sized kiobuf, that just means that we risk
> running out of kmaps. You need to treat kmaps as a scarce resource;
> on PAE36-configured machines we only have 512 of them right now.
I noticed that kmap ptes seem to be allocated from array of static size,
which is different to the method used for vmalloc(). Why is this?
--
dwmw2
--
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:45 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 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-28 18:45 ` David Woodhouse [this message]
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=Pine.LNX.4.21.0006281930220.987-100000@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=lord@sgi.com \
--cc=riel@conectiva.com.br \
--cc=sct@redhat.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