Re: [PATCH v2] mm: alloc_pages_bulk: remove assumption of populating only NULL elements

2025-03-15 Thread NeilBrown
On Mon, 10 Mar 2025, Yunsheng Lin wrote: > On 3/8/2025 5:02 AM, NeilBrown wrote: > > ... > > >> > >>>allocated pages in the array - just like the current > >>>alloc_pages_bulk(). > >> > >> I guess 'the total numbe

Re: [PATCH v2] mm: alloc_pages_bulk: remove assumption of populating only NULL elements

2025-03-07 Thread NeilBrown
On Fri, 07 Mar 2025, Yunsheng Lin wrote: > On 2025/3/7 5:14, NeilBrown wrote: > > On Thu, 06 Mar 2025, Yunsheng Lin wrote: > >> On 2025/3/6 7:41, NeilBrown wrote: > >>> On Wed, 05 Mar 2025, Yunsheng Lin wrote: > >>>> > >>>> Fo

Re: [PATCH v2] mm: alloc_pages_bulk: remove assumption of populating only NULL elements

2025-03-05 Thread NeilBrown
t need "more unified". If there are genuinely two different use cases with clearly different needs - even if only slightly different - then it is acceptable to have two different interfaces. Be sure to choose names which emphasise the differences. Thanks, NeilBrown

Re: [PATCH v2] mm: alloc_pages_bulk: remove assumption of populating only NULL elements

2025-03-06 Thread NeilBrown
On Thu, 06 Mar 2025, Yunsheng Lin wrote: > On 2025/3/6 7:41, NeilBrown wrote: > > On Wed, 05 Mar 2025, Yunsheng Lin wrote: > >> > >> For the existing btrfs and sunrpc case, I am agreed that there > >> might be valid use cases too, we just need to discuss

Re: [PATCH v2] mm: alloc_pages_bulk: remove assumption of populating only NULL elements

2025-03-11 Thread NeilBrown
re told how many pages had been stored in that array. A (very) few users benefit from the complexity. So having two interfaces, one simple and one full-featured, makes sense. Thanks, NeilBrown