Messages in this thread | | | Date | Fri, 14 Dec 2001 21:31:42 -0500 | From | Benjamin LaHaise <> | Subject | Re: zap_page_range in a module |
| |
On Fri, Dec 14, 2001 at 06:10:52PM -0800, Sottek, Matthew J wrote: > >The vm does zap_page_range for you if you're implementing an > >mmap operation, > > It only does zap_page_range() when the memory map is being > removed right?
Right.
> I have a 64k sliding "window" into a 1MB region. You can only access > 64k at a time then you have to switch the "bank" to access the next > 64k. Address 0xa0000-0xaffff is the 64k window. The actual 1MB of > memory is above the top of memory and not directly addressable by the > CPU, you have to go through the banks.
Stop right there. You can't do that. The code will deadlock on page faults for certain usage patterns. It's slow, inefficient and a waste of effort.
-ben -- Fish. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |