On Thu, Feb 11, 2021 at 01:26:28PM +0100, Jesper Dangaard Brouer wrote: > > Parameters to __rmqueue_pcplist are garbage as the parameter order changed. > > I'm surprised it didn't blow up in a spectacular fashion. Again, this > > hasn't been near any testing and passing a list with high orders to > > free_pages_bulk() will corrupt lists too. Mostly it's a curiousity to see > > if there is justification for reworking the allocator to fundamentally > > deal in batches and then feed batches to pcp lists and the bulk allocator > > while leaving the normal GFP API as single page "batches". While that > > would be ideal, it's relatively high risk for regressions. There is still > > some scope for adding a basic bulk allocator before considering a major > > refactoring effort. > > The alloc_flags reminds me that I have some asks around the semantics > of the API. I'm concerned about the latency impact on preemption. I > want us to avoid creating something that runs for too long with > IRQs/preempt disabled. > > (With SLUB kmem_cache_free_bulk() we manage to run most of the time with > preempt and IRQs enabled. So, I'm not worried about large slab bulk > free. For SLUB kmem_cache_alloc_bulk() we run with local_irq_disable(), > so I always recommend users not to do excessive bulk-alloc.) > The length of time IRQs/preempt disabled are partially related to the bulk API but the deeper concern is how long the IRQs are disabled within the page allocator in general. Sometimes they are disabled for list manipulations but the duration is longer than it has to be for per-cpu stat updates and that may be unnecessary for all arches and configurations. Some may need IRQs disabled but others may only need preempt disabled for the counters. That's a more serious overall than just the bulk allocator. > For this page bulk alloc API, I'm fine with limiting it to only support > order-0 pages. (This will also fit nicely with the PCP system it think). > Ok. > I also suggest the API can return less pages than requested. Because I > want to to "exit"/return if it need to go into an expensive code path > (like buddy allocator or compaction). I'm assuming we have a flags to > give us this behavior (via gfp_flags or alloc_flags)? > The API returns the number of pages returned on a list so policies around how aggressive it should be allocating the requested number of pages could be adjusted without changing the API. Passing in policy requests via gfp_flags may be problematic as most (all?) bits are already used. -- Mel Gorman SUSE Labs
