Linus Torvalds writes: (Summary) wrote:
Pretty much everything.
Pretty much everything.
It's the most complex part by far, and the vmalloc space is a limited resource on 32-bit architectures.
resource on 32-bit architectures.
Do everything in user space.
Do everything in user space.
And even if you absolutely want cpu_opv at all, why not do it in the user space *mapping* without the aliasing into kernel space? user space *mapping* without the aliasing into kernel space?
[...]
What are your concerns about page pinning ?Pretty much everything.
Pretty much everything.
It's the most complex part by far, and the vmalloc space is a limited resource on 32-bit architectures.
resource on 32-bit architectures.
[...]
Do you have an alternative approach in mind ?Do everything in user space.
Do everything in user space.
And even if you absolutely want cpu_opv at all, why not do it in the user space *mapping* without the aliasing into kernel space? user space *mapping* without the aliasing into kernel space?