On 27/03/2014 22:23, Chris Wilson wrote:
On Thu, Mar 27, 2014 at 03:28:26PM +0000, arun.siluvery@xxxxxxxxxxxxxxx wrote:
From: "Siluvery, Arun" <arun.siluvery@xxxxxxxxx>
This patch series adds a new ioctl to resize a gem object.
I'm tired, but off the top of my head, I think you can do away with the
magic extension to create_ioctl. If we allow any one to fallocate()
ranges of any object, the user can create a large object, populate it
all with a scratch page, then later populate regions as required. This
looks quite a reasonable and useful feature.
-Chris
Sorry for the delayed response, I was on holiday. I will modify the
implementation to use fallocate(), shmem is supporting this and it seems
to be a better approach.
In this case once the object is created we extend gem_create ioctl using
fallocate() and allocate the additional space but does the userspace
still see it as a contiguous block when it writes to the additional space?
Once the object is modified using fallocate(), are these changes
completely transparent when this object is used in other functions?
please clarify.
regards
Arun
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
