On Mon, Apr 20, 2020 at 1:22 AM Christian Brauner christian.brauner@ubuntu.com wrote:
On Thu, Apr 16, 2020 at 12:25:08PM +0200, Greg Kroah-Hartman wrote:
On Tue, Apr 14, 2020 at 09:41:31PM -0700, John Stultz wrote:
But I do think we can mark it as deprecated and let folks know that around the end of the year it will be deleted.
No one ever notices "depreciated" things, they only notice if the code is no longer there :)
So I'm all for just deleting it and seeing who even notices...
Agreed.
I mean, I get there's not much love for ION in staging, and I too am eager to see it go, but I also feel like in the discussions around submitting the dmabuf heaps at talks, etc, that there was clear value in removing ION after a short time so that folks could transition being able to test both implementations against the same kernel so performance regressions, etc could be worked out.
I am actively getting many requests for help for vendors who are looking at dmabuf heaps and are starting the transition process, and I'm trying my best to motivate them to directly work within the community so their needed heap functionality can go upstream. But it's going to be a process, and their first attempts aren't going to magically land upstream. I think being able to really compare their implementations as they iterate and push things upstream will help in order to be able to have upstream solutions that are also properly functional for production usage.
The dmabuf heaps have been in an official kernel now for all of three weeks. So yea, we can "delete [ION] and see who even notices", but I worry that may seem a bit like contempt for the folks doing the work on transitioning over, which doesn't help getting them to participate within the community.
thanks -john
On Mon, Apr 20, 2020 at 01:03:39PM -0700, John Stultz wrote:
On Mon, Apr 20, 2020 at 1:22 AM Christian Brauner christian.brauner@ubuntu.com wrote:
On Thu, Apr 16, 2020 at 12:25:08PM +0200, Greg Kroah-Hartman wrote:
On Tue, Apr 14, 2020 at 09:41:31PM -0700, John Stultz wrote:
But I do think we can mark it as deprecated and let folks know that around the end of the year it will be deleted.
No one ever notices "depreciated" things, they only notice if the code is no longer there :)
So I'm all for just deleting it and seeing who even notices...
Agreed.
I mean, I get there's not much love for ION in staging, and I too am eager to see it go, but I also feel like in the discussions around submitting the dmabuf heaps at talks, etc, that there was clear value in removing ION after a short time so that folks could transition being able to test both implementations against the same kernel so performance regressions, etc could be worked out.
I am actively getting many requests for help for vendors who are looking at dmabuf heaps and are starting the transition process, and I'm trying my best to motivate them to directly work within the community so their needed heap functionality can go upstream. But it's going to be a process, and their first attempts aren't going to magically land upstream. I think being able to really compare their implementations as they iterate and push things upstream will help in order to be able to have upstream solutions that are also properly functional for production usage.
But we are not accepting any new ion allocators or changes at the moment, so I don't see how the ion code in the kernel is helping/hurting anything here.
There has been a bunch of changes to the ion code recently, in the Android kernel trees, in order to get a lot of the different manufacturer "forks" of ion back together into one place. But again, those patches are not going to be sent upstream for merging so how is ion affecting the dmabuf code at all here?
The dmabuf heaps have been in an official kernel now for all of three weeks. So yea, we can "delete [ION] and see who even notices", but I worry that may seem a bit like contempt for the folks doing the work on transitioning over, which doesn't help getting them to participate within the community.
But they aren't participating in the community today as no one is touching the ion code. So I fail to see how keeping a dead-end-version of ion in the kernel tree really affects anyone these days.
thanks,
greg k-h
On Tue, Apr 21, 2020 at 10:05:44AM +0200, Greg Kroah-Hartman wrote:
On Mon, Apr 20, 2020 at 01:03:39PM -0700, John Stultz wrote:
On Mon, Apr 20, 2020 at 1:22 AM Christian Brauner christian.brauner@ubuntu.com wrote:
On Thu, Apr 16, 2020 at 12:25:08PM +0200, Greg Kroah-Hartman wrote:
On Tue, Apr 14, 2020 at 09:41:31PM -0700, John Stultz wrote:
But I do think we can mark it as deprecated and let folks know that around the end of the year it will be deleted.
No one ever notices "depreciated" things, they only notice if the code is no longer there :)
So I'm all for just deleting it and seeing who even notices...
Agreed.
I mean, I get there's not much love for ION in staging, and I too am eager to see it go, but I also feel like in the discussions around submitting the dmabuf heaps at talks, etc, that there was clear value in removing ION after a short time so that folks could transition being able to test both implementations against the same kernel so performance regressions, etc could be worked out.
I am actively getting many requests for help for vendors who are looking at dmabuf heaps and are starting the transition process, and I'm trying my best to motivate them to directly work within the community so their needed heap functionality can go upstream. But it's going to be a process, and their first attempts aren't going to magically land upstream. I think being able to really compare their implementations as they iterate and push things upstream will help in order to be able to have upstream solutions that are also properly functional for production usage.
But we are not accepting any new ion allocators or changes at the moment, so I don't see how the ion code in the kernel is helping/hurting anything here.
There has been a bunch of changes to the ion code recently, in the Android kernel trees, in order to get a lot of the different manufacturer "forks" of ion back together into one place. But again, those patches are not going to be sent upstream for merging so how is ion affecting the dmabuf code at all here?
The dmabuf heaps have been in an official kernel now for all of three weeks. So yea, we can "delete [ION] and see who even notices", but I worry that may seem a bit like contempt for the folks doing the work on transitioning over, which doesn't help getting them to participate within the community.
But they aren't participating in the community today as no one is touching the ion code. So I fail to see how keeping a dead-end-version of ion in the kernel tree really affects anyone these days.
So, any thoughts here? What's the timeline for ion being able to be removed that you are comfortable with?
thanks,
greg k-h
On Fri, Jul 3, 2020 at 12:03 AM Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Tue, Apr 21, 2020 at 10:05:44AM +0200, Greg Kroah-Hartman wrote:
On Mon, Apr 20, 2020 at 01:03:39PM -0700, John Stultz wrote:
The dmabuf heaps have been in an official kernel now for all of three weeks. So yea, we can "delete [ION] and see who even notices", but I worry that may seem a bit like contempt for the folks doing the work on transitioning over, which doesn't help getting them to participate within the community.
But they aren't participating in the community today as no one is touching the ion code. So I fail to see how keeping a dead-end-version of ion in the kernel tree really affects anyone these days.
So, any thoughts here? What's the timeline for ion being able to be removed that you are comfortable with?
Sorry for the slow reply. So my earlier plan was to drop it after the next LTS?
thanks -john
On Tue, Jul 07, 2020 at 08:43:30PM -0700, John Stultz wrote:
On Fri, Jul 3, 2020 at 12:03 AM Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Tue, Apr 21, 2020 at 10:05:44AM +0200, Greg Kroah-Hartman wrote:
On Mon, Apr 20, 2020 at 01:03:39PM -0700, John Stultz wrote:
The dmabuf heaps have been in an official kernel now for all of three weeks. So yea, we can "delete [ION] and see who even notices", but I worry that may seem a bit like contempt for the folks doing the work on transitioning over, which doesn't help getting them to participate within the community.
But they aren't participating in the community today as no one is touching the ion code. So I fail to see how keeping a dead-end-version of ion in the kernel tree really affects anyone these days.
So, any thoughts here? What's the timeline for ion being able to be removed that you are comfortable with?
Sorry for the slow reply. So my earlier plan was to drop it after the next LTS?
Ok, fair enough, we can wait until January.
thanks,
greg k-h
linaro-mm-sig@lists.linaro.org
-
Greg Kroah-Hartman -
John Stultz