All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Kevin Hao <haokexin@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH net-next 1/4] mm: page_frag: Introduce page_frag_alloc_align()
Date: Tue, 26 Jan 2021 17:19:54 +0100	[thread overview]
Message-ID: <42fecf9d-70c9-b686-d2f7-080b299060d9@suse.cz> (raw)
In-Reply-To: <20210123115903.31302-2-haokexin@gmail.com>

On 1/23/21 12:59 PM, Kevin Hao wrote:
> In the current implementation of page_frag_alloc(), it doesn't have
> any align guarantee for the returned buffer address. But for some
> hardwares they do require the DMA buffer to be aligned correctly,
> so we would have to use some workarounds like below if the buffers
> allocated by the page_frag_alloc() are used by these hardwares for
> DMA.
>     buf = page_frag_alloc(really_needed_size + align);
>     buf = PTR_ALIGN(buf, align);
> 
> These codes seems ugly and would waste a lot of memories if the buffers
> are used in a network driver for the TX/RX. So introduce
> page_frag_alloc_align() to make sure that an aligned buffer address is
> returned.
> 
> Signed-off-by: Kevin Hao <haokexin@gmail.com>

Acked-by: Vlastimil Babka <vbabka@suse.cz>

Agree with Jakub about static inline.

> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -5135,8 +5135,8 @@ void __page_frag_cache_drain(struct page *page, unsigned int count)
>  }
>  EXPORT_SYMBOL(__page_frag_cache_drain);
>  
> -void *page_frag_alloc(struct page_frag_cache *nc,
> -		      unsigned int fragsz, gfp_t gfp_mask)
> +void *page_frag_alloc_align(struct page_frag_cache *nc,
> +		      unsigned int fragsz, gfp_t gfp_mask, int align)
>  {
>  	unsigned int size = PAGE_SIZE;
>  	struct page *page;
> @@ -5188,10 +5188,18 @@ void *page_frag_alloc(struct page_frag_cache *nc,
>  	}
>  
>  	nc->pagecnt_bias--;
> +	offset = align ? ALIGN_DOWN(offset, align) : offset;

We don't change offset if align == 0, so I'd go with simpler
if (align)
	offset = ...

>  	nc->offset = offset;
>  
>  	return nc->va + offset;
>  }
> +EXPORT_SYMBOL(page_frag_alloc_align);
> +
> +void *page_frag_alloc(struct page_frag_cache *nc,
> +		      unsigned int fragsz, gfp_t gfp_mask)
> +{
> +	return page_frag_alloc_align(nc, fragsz, gfp_mask, 0);
> +}
>  EXPORT_SYMBOL(page_frag_alloc);
>  
>  /*
> 



  parent reply	other threads:[~2021-01-26 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-23 11:58 [PATCH net-next 0/4] net: Avoid the memory waste in some Ethernet drivers Kevin Hao
2021-01-23 11:59 ` [PATCH net-next 1/4] mm: page_frag: Introduce page_frag_alloc_align() Kevin Hao
2021-01-23 20:52   ` Jakub Kicinski
2021-01-24  3:55     ` Kevin Hao
2021-01-26 16:19   ` Vlastimil Babka [this message]
2021-01-23 11:59 ` [PATCH net-next 2/4] net: Introduce {netdev,napi}_alloc_frag_align() Kevin Hao
2021-01-23 11:59 ` [PATCH net-next 3/4] net: octeontx2: Use napi_alloc_frag_align() to avoid the memory waste Kevin Hao
2021-01-23 11:59 ` [PATCH net-next 4/4] net: dpaa2: " Kevin Hao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42fecf9d-70c9-b686-d2f7-080b299060d9@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=haokexin@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.