search for: gemf

Displaying 5 results from an estimated 5 matches for "gemf".

Did you mean: gem
2015 Jul 09
1
[RFCv3 0/5] enable migration of driver pages
...rivers since our backing > storage is shmemfs. So if we want to implement page migration (which we'd > probably want to make large pages work well) we'd need to pimp shmem to a) > hand large pages to us b) forward the migrate calls. Probably that means > we need to build our own gemfs reusing shmemfs code. AFAIK there are efforts ongoing to make large pages work with shmem. Kirill, IIRC you mentioned that you're were looking into this a while back? -- Ville Syrj?l? Intel OTC
2015 Jul 09
1
[RFCv3 0/5] enable migration of driver pages
...rivers since our backing > storage is shmemfs. So if we want to implement page migration (which we'd > probably want to make large pages work well) we'd need to pimp shmem to a) > hand large pages to us b) forward the migrate calls. Probably that means > we need to build our own gemfs reusing shmemfs code. AFAIK there are efforts ongoing to make large pages work with shmem. Kirill, IIRC you mentioned that you're were looking into this a while back? -- Ville Syrj?l? Intel OTC
2015 Jul 08
3
[RFCv3 0/5] enable migration of driver pages
2015-07-09 ?? 7:47? Dave Airlie ?(?) ? ?: >>> >>> >>> Can the various in-kernel GPU drivers benefit from this? If so, wiring >>> up one or more of those would be helpful? >> >> >> I'm sure that other in-kernel GPU drivers can have benefit. >> It must be helpful. >> >> If I was familiar with other in-kernel GPU drivers
2015 Jul 08
3
[RFCv3 0/5] enable migration of driver pages
2015-07-09 ?? 7:47? Dave Airlie ?(?) ? ?: >>> >>> >>> Can the various in-kernel GPU drivers benefit from this? If so, wiring >>> up one or more of those would be helpful? >> >> >> I'm sure that other in-kernel GPU drivers can have benefit. >> It must be helpful. >> >> If I was familiar with other in-kernel GPU drivers
2015 Jul 09
0
[RFCv3 0/5] enable migration of driver pages
...fit for gem based drivers since our backing storage is shmemfs. So if we want to implement page migration (which we'd probably want to make large pages work well) we'd need to pimp shmem to a) hand large pages to us b) forward the migrate calls. Probably that means we need to build our own gemfs reusing shmemfs code. I guess something similar would apply for ttm-based drivers (which use shmemfs just for swap-in/out but otherwise have their own page allocator, at least sometimes). Given all that I'd expect anything implementing migrate to just create a gpufs thing for the backing sto...