From: William Lee Irwin III <wli@holomorphy.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Dave Hansen <haveblue@us.ibm.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: How best to bypass the page cache from within a kernel module?
Date: Wed, 17 Sep 2003 13:40:47 -0700 [thread overview]
Message-ID: <20030917204047.GI14079@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0309171617560.1646-100000@ida.rowland.org>
On Wed, Sep 17, 2003 at 04:33:08PM -0400, Alan Stern wrote:
> I really want this to work through the filesystem. 99% of what my driver
> does involves normal reads and writes. And there are very good reasons
> for having it run as a kernel thread rather than a user process. It's
> just that this one piece, which is a very minor part of the driver, needs
> to avoid the page cache.
> So to reiterate my original questions:
Doesn't sound much most drivers after all that, but there's some weird
stuff out there.
On Wed, Sep 17, 2003 at 04:33:08PM -0400, Alan Stern wrote:
> 1. What's the proper way for a kernel thread running in a module to get
> hold of an mm_struct or to keep the one it had before calling daemonize()?
Well, you can get one from the slab allocator, though I expect there will
be a followup question here...
On Wed, Sep 17, 2003 at 04:33:08PM -0400, Alan Stern wrote:
> 2. What's the proper way for a kernel thread to allocate a region of
> userspace memory?
Hmm. Sounds like you want to grab a user address space and do userspace
stuff inside there. Maybe avoid do_execve() etc. and call sys_*() for
everything else outright? The question itself probably wants sys_mmap()
or some such, or handle_mm_fault() depending on what you have in mind
for allocation.
On Wed, Sep 17, 2003 at 04:33:08PM -0400, Alan Stern wrote:
> 3. What's the proper way to invalidate all entries in the page cache
> that refer to a particular file?
invalidate_inode_pages().
-- wli
--
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-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-09-17 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 18:24 How best to bypass the page cache from within a kernel module? Alan Stern
2003-09-17 19:44 ` Dave Hansen
2003-09-17 19:50 ` William Lee Irwin III
2003-09-17 20:33 ` Alan Stern
2003-09-17 20:40 ` William Lee Irwin III [this message]
2003-09-17 20:43 ` William Lee Irwin III
2003-09-17 21:30 ` Alan Stern
2003-09-17 22:44 ` William Lee Irwin III
2003-09-22 18:51 ` Ray Bryant
2003-09-22 19:09 ` Alan Stern
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=20030917204047.GI14079@holomorphy.com \
--to=wli@holomorphy.com \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.