linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: William Lee Irwin III <wli@holomorphy.com>
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 16:33:08 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.0309171617560.1646-100000@ida.rowland.org> (raw)
In-Reply-To: <20030917195044.GH14079@holomorphy.com>

> On Wed, 2003-09-17 at 11:24, Alan Stern wrote:
> > However, all that seems rather roundabout.  An equally acceptable solution 
> > would be simply to invalidate all the entries in the page cache referring 
> > to my file, so that reads would be forced to go to the drive.  Can anyone 
> > tell me how to do that?

On Wed, Sep 17, 2003 at 12:44:29PM -0700, Dave Hansen wrote:
> Whatever you're trying to do, you probably shouldn't be doing it in the
> kernel to begin with.  Do it from userspace, it will save you a lot of
> pain.

That's not particularly helpful, especially considering that the entire
driver currently works just fine as a kernel module, with the exception of
this one piece.  (This one piece works too; it just doesn't do exactly 
what I want.)

On Wed, 17 Sep 2003, William Lee Irwin III wrote:
> If you really want to bypass the pagecache etc. entirely, use raw io and
> don't even bother mounting the filesystem, and do it all from userspace.
> If you need it simultaneously mounted then you're in somewhat deeper
> trouble, though you can probably be rescued by nefarious means like that
> bit about shooting down the pagecache so you don't have some incoherent
> cache headache.

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:

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()?

2. What's the proper way for a kernel thread to allocate a region of 
userspace memory?

3. What's the proper way to invalidate all entries in the page cache that 
refer to a particular file?

Alan Stern

--
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>

  reply	other threads:[~2003-09-17 20:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-17 18:24 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 [this message]
2003-09-17 20:40       ` William Lee Irwin III
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=Pine.LNX.4.44L0.0309171617560.1646-100000@ida.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=haveblue@us.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=wli@holomorphy.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