| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <e38cc22e-afbc-445e-b986-9ab31c799a09@gmail.com>
Date: Sat, 19 Oct 2024 16:29:55 +0800
From: Yunsheng Lin <yunshenglin0825@...il.com>
To: Alexander Duyck <alexander.duyck@...il.com>,
Yunsheng Lin <linyunsheng@...wei.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org
Subject: Re: [PATCH net-next v22 07/14] mm: page_frag: some minor refactoring
before adding new API
On 10/19/2024 1:26 AM, Alexander Duyck wrote:
...
>> +static inline void *__page_frag_alloc_align(struct page_frag_cache *nc,
>> + unsigned int fragsz, gfp_t gfp_mask,
>> + unsigned int align_mask)
>> +{
>> + struct page_frag page_frag;
>> + void *va;
>> +
>> + va = __page_frag_cache_prepare(nc, fragsz, &page_frag, gfp_mask,
>> + align_mask);
>> + if (unlikely(!va))
>> + return NULL;
>> +
>> + __page_frag_cache_commit(nc, &page_frag, fragsz);
>
> Minor nit here. Rather than if (!va) return I think it might be better
> to just go with if (likely(va)) __page_frag_cache_commit.
Ack.
>
>> +
>> + return va;
>> +}
>>
>> static inline void *page_frag_alloc_align(struct page_frag_cache *nc,
>> unsigned int fragsz, gfp_t gfp_mask,
>> diff --git a/mm/page_frag_cache.c b/mm/page_frag_cache.c
>> index a36fd09bf275..a852523bc8ca 100644
>> --- a/mm/page_frag_cache.c
>> +++ b/mm/page_frag_cache.c
>> @@ -90,9 +90,31 @@ void __page_frag_cache_drain(struct page *page, unsigned int count)
>> }
>> EXPORT_SYMBOL(__page_frag_cache_drain);
>>
>> -void *__page_frag_alloc_align(struct page_frag_cache *nc,
>> - unsigned int fragsz, gfp_t gfp_mask,
>> - unsigned int align_mask)
>> +unsigned int __page_frag_cache_commit_noref(struct page_frag_cache *nc,
>> + struct page_frag *pfrag,
>> + unsigned int used_sz)
>> +{
>> + unsigned int orig_offset;
>> +
>> + VM_BUG_ON(used_sz > pfrag->size);
>> + VM_BUG_ON(pfrag->page != encoded_page_decode_page(nc->encoded_page));
>> + VM_BUG_ON(pfrag->offset + pfrag->size >
>> + (PAGE_SIZE << encoded_page_decode_order(nc->encoded_page)));
>> +
>> + /* pfrag->offset might be bigger than the nc->offset due to alignment */
>> + VM_BUG_ON(nc->offset > pfrag->offset);
>> +
>> + orig_offset = nc->offset;
>> + nc->offset = pfrag->offset + used_sz;
>> +
>> + /* Return true size back to caller considering the offset alignment */
>> + return nc->offset - orig_offset;
>> +}
>> +EXPORT_SYMBOL(__page_frag_cache_commit_noref);
>> +
>
> I have a question. How often is it that we are committing versus just
> dropping the fragment? It seems like this approach is designed around
> optimizing for not commiting the page as we are having to take an
> extra function call to commit the change every time. Would it make
> more sense to have an abort versus a commit?
Before this patch, page_frag_alloc() related API seems to be mostly used
for skb data or frag for rx part, see napi_alloc_skb() or some drivers
like e1000, but with more drivers using the page_pool for skb rx frag,
it seems skb data for tx is the main usecase.
And the prepare and commit API added in the patchset seems to be mainly
used for skb frag for tx part except af_packet.
It seems it is not very clear which is mostly used one, mostly likely
the prepare and commit API might be the mostly used one if I have to
guess as there might be more memory needed for skb frag than skb data.
>
>> +void *__page_frag_cache_prepare(struct page_frag_cache *nc, unsigned int fragsz,
>> + struct page_frag *pfrag, gfp_t gfp_mask,
>> + unsigned int align_mask)
>> {
>> unsigned long encoded_page = nc->encoded_page;
>> unsigned int size, offset;
>> @@ -114,6 +136,8 @@ void *__page_frag_alloc_align(struct page_frag_cache *nc,
>> /* reset page count bias and offset to start of new frag */
>> nc->pagecnt_bias = PAGE_FRAG_CACHE_MAX_SIZE + 1;
>> nc->offset = 0;
>> + } else {
>> + page = encoded_page_decode_page(encoded_page);
>> }
>>
>> size = PAGE_SIZE << encoded_page_decode_order(encoded_page);
>
> This makes no sense to me. Seems like there are scenarios where you
> are grabbing the page even if you aren't going to use it? Why?
>
> I think you would be better off just waiting to the end and then
> fetching it instead of trying to grab it and potentially throw it away
> if there is no space left in the page. Otherwise what you might do is
> something along the lines of:
> pfrag->page = page ? : encoded_page_decode_page(encoded_page);
But doesn't that mean an additional checking is needed to decide if we
need to grab the page?
But the './scripts/bloat-o-meter' does show some binary size shrink
using the above.
>
>
>> @@ -132,8 +156,6 @@ void *__page_frag_alloc_align(struct page_frag_cache *nc,
>> return NULL;
>> }
>>
>> - page = encoded_page_decode_page(encoded_page);
>> -
>> if (!page_ref_sub_and_test(page, nc->pagecnt_bias))
>> goto refill;
>>
>> @@ -148,15 +170,17 @@ void *__page_frag_alloc_align(struct page_frag_cache *nc,
>>
>> /* reset page count bias and offset to start of new frag */
>> nc->pagecnt_bias = PAGE_FRAG_CACHE_MAX_SIZE + 1;
>> + nc->offset = 0;
>> offset = 0;
>> }
>>
>> - nc->pagecnt_bias--;
>> - nc->offset = offset + fragsz;
>> + pfrag->page = page;
>> + pfrag->offset = offset;
>> + pfrag->size = size - offset;
>
> I really think we should still be moving the nc->offset forward at
> least with each allocation. It seems like you end up doing two flavors
> of commit, one with and one without the decrement of the bias. So I
> would be okay with that being pulled out into some separate logic to
> avoid the extra increment in the case of merging the pages. However in
> both cases you need to move the offset, so I would recommend keeping
> that bit there as it would allow us to essentially call this multiple
> times without having to do a commit in between to keep the offset
> correct. With that your commit logic only has to verify nothing
> changes out from underneath us and then update the pagecnt_bias if
> needed.
The problem is that we don't really know how much the nc->offset
need to be moved forward to and the caller needs the original offset
for skb_fill_page_desc() related calling when prepare API is used as
an example in 'Preparation & committing API' section of patch 13:
+Preparation & committing API
+----------------------------
+
+.. code-block:: c
+
+ struct page_frag page_frag, *pfrag;
+ bool merge = true;
+ void *va;
+
+ pfrag = &page_frag;
+ va = page_frag_alloc_refill_prepare(nc, 32U, pfrag, GFP_KERNEL);
+ if (!va)
+ goto wait_for_space;
+
+ copy = min_t(unsigned int, copy, pfrag->size);
+ if (!skb_can_coalesce(skb, i, pfrag->page, pfrag->offset)) {
+ if (i >= max_skb_frags)
+ goto new_segment;
+
+ merge = false;
+ }
+
+ copy = mem_schedule(copy);
+ if (!copy)
+ goto wait_for_space;
+
+ err = copy_from_iter_full_nocache(va, copy, iter);
+ if (err)
+ goto do_error;
+
+ if (merge) {
+ skb_frag_size_add(&skb_shinfo(skb)->frags[i - 1], copy);
+ page_frag_commit_noref(nc, pfrag, copy);
+ } else {
+ skb_fill_page_desc(skb, i, pfrag->page, pfrag->offset, copy);
+ page_frag_commit(nc, pfrag, copy);
+ }
Powered by blists - more mailing lists