Messages in this thread | | | From | "Stephen C. Tweedie" <> | Date | Fri, 12 Nov 1999 02:03:39 +0000 (GMT) | Subject | Re: kiobuf using kernel pages |
| |
Hi,
On Thu, 11 Nov 1999 08:55:54 -0800 (PST), Matt Robinson <yakker@cthulhu.engr.sgi.com> said:
> We agree it's a violation in the worst sense. :) The problem is there > was no good way to set AS_KERNEL without calling map_user_kiobuf() on > your own. Until such a scheme is put in place (which we believe will be > at some point soon), we put something in to make it work for us. It's > certainly better than a conditional check in map_user_kiobuf(). :)
Umm, why do you need this at all? The caller is either file IO --- in which case you just do the map_user_kiobuf and pass that to the kiovec IO routine --- or it is kernel-originated IO, in which case you create a kiobuf of your own and just stuff it full of references to the kernel pages you want to read or write.
The low-level IO function should never, ever have to care about what address space the kiobuf is coming from. That's the whole point of kiobufs.
--Stephen
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |