On Fri, 26 Apr 2019 08:19:03 -0700 Jacob Pan <[email protected]> wrote:
> > >>> + default_allocator_used = 1; > > >> shouldn't default_allocator_used be protected as well? > > [...] > > >> wouldn't it be possible to integrate the default io asid > > >> allocator as any custom allocator, ie. implement an alloc > > >> callback using xa_alloc. Then the active io allocator could be > > >> either a custom or a default one. > > > That is an interesting idea. I think it is possible. > > > But since default xa allocator is internal to ioasid > > > infrastructure, why implement it as a callback? > > > > I mean your could directly define a static const default_allocator > > in ioasid.c and assign it by default. Do I miss something? > > > got it, seems cleaner. let me give it a try. Hi Eric, Just sent out v3 last week. I did look into this but could not find a clean way of making the default allocator as another custom allocator. The reason is that default allocator is not interchangeable with other custom allocators, XArray is shared. So it ends up having lots of special cases anyway. Feel free to change this. Thanks, Jacob _______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu
