Re: [PATCH v2 0/7] Kernel huge I/O mapping support

2015-03-02 Thread Toshi Kani
On Tue, 2015-02-24 at 09:09 +0100, Ingo Molnar wrote: > * Andrew Morton wrote: > > > > > > > Oh. We don't do any checking at all. We're just telling > > userspace programmers "don't do that". hrm. What are > > your thoughts on adding the overlap checks to the kernel? > > I have requested

Re: [PATCH v2 0/7] Kernel huge I/O mapping support

2015-02-24 Thread Ingo Molnar
* Andrew Morton wrote: > > > Oh. We don't do any checking at all. We're just telling > userspace programmers "don't do that". hrm. What are > your thoughts on adding the overlap checks to the kernel? I have requested such sanity checking in previous review as well, it has to be made fo

Re: [PATCH v2 0/7] Kernel huge I/O mapping support

2015-02-23 Thread Toshi Kani
On Mon, 2015-02-23 at 12:22 -0800, Andrew Morton wrote: > On Mon, 9 Feb 2015 15:45:28 -0700 Toshi Kani wrote: > > > ioremap() and its related interfaces are used to create I/O > > mappings to memory-mapped I/O devices. The mapping sizes of > > the traditional I/O devices are relatively small.

Re: [PATCH v2 0/7] Kernel huge I/O mapping support

2015-02-23 Thread Andrew Morton
On Mon, 9 Feb 2015 15:45:28 -0700 Toshi Kani wrote: > ioremap() and its related interfaces are used to create I/O > mappings to memory-mapped I/O devices. The mapping sizes of > the traditional I/O devices are relatively small. Non-volatile > memory (NVM), however, has many GB and is going to

[PATCH v2 0/7] Kernel huge I/O mapping support

2015-02-09 Thread Toshi Kani
ioremap() and its related interfaces are used to create I/O mappings to memory-mapped I/O devices. The mapping sizes of the traditional I/O devices are relatively small. Non-volatile memory (NVM), however, has many GB and is going to have TB soon. It is not very efficient to create large I/O mapp