From: Mark Hounschell <markh@compro.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mlockall and mmap of IO devices don't mix
Date: Fri, 16 Jul 2004 17:01:00 -0400 [thread overview]
Message-ID: <40F8420C.88E694F2@compro.net> (raw)
In-Reply-To: 20040525124715.5f7e61b6.akpm@osdl.org
Andrew Morton wrote:
>
> Joe Korty <joe.korty@ccur.com> wrote:
> >
> > On Fri, May 21, 2004 at 07:13:26PM -0700, Andrew Morton wrote:
> > > Mark Hounschell <markh@compro.net> wrote:
> > > >
> > > > Joe Korty wrote:
> > > > >
> > > > > 2.6.0-test6: the use of mlockall(2) in a process that has mmap(2)ed
> > > > > the registers of an IO device will hang that process uninterruptibly.
> > > > > The task runs in an infinite loop in get_user_pages(), invoking
> > > > > follow_page() forever.
> > > > >
> > > > > Using binary search I discovered that the problem was introduced
> > > > > in 2.5.14, specifically in ChangeSetKey
> > > > >
> > > > > zippel@linux-m68k.org|ChangeSet|20020503210330|37095
> > > > >
> > > >
> > > > I know this is an old thread but can anyone tell me if this problem is
> > > > resolved in the current 2.6.6 kernel?
> > > >
> > >
> > > There's an utterly ancient patch in -mm which might fix this.
> > >
> > > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.6.6-mm4/broken-out/get_user_pages-handle-VM_IO.patch
> >
> > [ 2nd send -- corporate email system in the throes of being scrambled / updated ]
> >
> > Andrew,
> > I have been using this patch for ages. Any chance of it being forwared to
> > the official tree?
>
> That patch had its first birthday last week. I wrote it in response to
> some long-forgotten problem, failed to changelog it at the time then forgot
> why I wrote it. I kept it in the hope that I'd remember why I wrote it. I
> subsequently wrote a best-effort changelog but am unconvinced by it. Ho
> hum.
>
> Let me genuflect a bit. I guess we can be reasonably confident it won't
> break anything.
Strange thing about this patch is "it doesn't seem to work on all
machines". Originally it worked for me on a dual AMD1900 box. Now I'm
trying to use it on a Dual P4 box and a dual Opteron in both 32 and 64
bit modes with no luck at all???? I guess I need to go back to my
original AMD and reverify it's functionality.
The user level code I'm using:
status = mlockall(MCL_CURRENT | MCL_FUTURE);
if (status < 0)
perror("mlock all failure");
dhan = rtom_usec_map(&rtom_microseconds, 0); mmaps rtom usec timer
?????
Regards
Mark
next prev parent reply other threads:[~2004-07-16 21:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 21:44 mlockall and mmap of IO devices don't mix Joe Korty
2003-10-03 22:23 ` Andrew Morton
2003-10-03 22:55 ` Joe Korty
2003-10-03 23:06 ` Andrew Morton
2003-10-03 23:28 ` Joe Korty
2003-10-03 23:15 ` Andrew Morton
2003-10-03 23:54 ` Joe Korty
2003-10-04 0:27 ` Andrew Morton
2003-10-04 5:47 ` David S. Miller
2003-10-04 9:29 ` Ingo Oeser
2004-05-21 11:34 ` Mark Hounschell
2004-05-22 2:13 ` Andrew Morton
2004-05-22 10:47 ` Mark Hounschell
2004-05-23 12:58 ` Mark Hounschell
2004-05-25 14:27 ` Joe Korty
2004-05-25 19:47 ` Andrew Morton
2004-05-25 21:31 ` Joe Korty
2004-07-16 21:01 ` Mark Hounschell [this message]
[not found] <CFYv.787.23@gated-at.bofh.it>
2003-10-04 7:02 ` Andi Kleen
2003-10-04 7:42 ` Andrew Morton
2003-10-04 8:29 ` Andi Kleen
2003-10-04 8:47 ` Ingo Oeser
2003-10-04 9:17 ` Andi Kleen
2003-10-04 9:22 ` Russell King
2003-10-04 10:02 ` Ingo Oeser
2003-10-04 10:13 ` Russell King
2003-10-04 14:19 ` Ingo Oeser
2003-10-04 14:19 ` Ingo Oeser
2003-10-04 14:32 ` Martin J. Bligh
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=40F8420C.88E694F2@compro.net \
--to=markh@compro.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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.