linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Liang Chen <liangchen.linux@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	 pabeni@redhat.com, hawk@kernel.org, linyunsheng@huawei.com,
	 netdev@vger.kernel.org, linux-mm@kvack.org, jasowang@redhat.com
Subject: Re: [PATCH net-next v6 4/4] skbuff: Optimization of SKB coalescing for page pool
Date: Fri, 1 Dec 2023 12:34:50 +0200	[thread overview]
Message-ID: <CAC_iWj+ku5Mk99ezVdC4HhNWK=Ea83Ps-qaQq=_-fzVoWZ8sYQ@mail.gmail.com> (raw)
In-Reply-To: <20231130115611.6632-5-liangchen.linux@gmail.com>

HI Liang,

[...]

>  }
>
> +/**
> + * skb_pp_frag_ref() - Increase fragment reference count of a page
> + * @page:      page of the fragment on which to increase a reference
> + *
> + * Increase fragment reference count (pp_ref_count) on a page, but if it is
> + * not a page pool page, fallback to increase a reference(_refcount) on a
> + * normal page.
> + */
> +static void skb_pp_frag_ref(struct page *page)
> +{
> +       struct page *head_page = compound_head(page);
> +
> +       if (likely(skb_frag_is_pp_page(head_page)))
> +               page_pool_ref_page(head_page);
> +       else
> +               page_ref_inc(head_page);

I think I've mentioned this in the past, but I think shoehorning page
pool awareness in the skbuff is not the direction we want to go. Up to
now, we've tried hard to make that as seamless as possible.
The code looks correct, but I'd prefer people with a better
understanding of the core network stack to comment on this.

[...]

Thanks
/Ilias


      reply	other threads:[~2023-12-01 10:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 11:56 [PATCH net-next v6 0/4] skbuff: Optimize " Liang Chen
2023-11-30 11:56 ` [PATCH net-next v6 1/4] page_pool: Rename pp_frag_count to pp_ref_count Liang Chen
2023-12-01  9:59   ` Ilias Apalodimas
2023-12-01 10:10     ` Ilias Apalodimas
2023-12-02  2:19       ` Jakub Kicinski
2023-12-04  2:39       ` Liang Chen
2023-11-30 11:56 ` [PATCH net-next v6 2/4] page_pool: halve BIAS_MAX for multiple user references of a fragment Liang Chen
2023-11-30 11:56 ` [PATCH net-next v6 3/4] skbuff: Add a function to check if a page belongs to page_pool Liang Chen
2023-12-01 10:07   ` Ilias Apalodimas
2023-12-01 10:22   ` Ilias Apalodimas
2023-12-04  2:40     ` Liang Chen
2023-12-05 11:02       ` Ilias Apalodimas
2023-11-30 11:56 ` [PATCH net-next v6 4/4] skbuff: Optimization of SKB coalescing for page pool Liang Chen
2023-12-01 10:34   ` Ilias Apalodimas [this message]

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='CAC_iWj+ku5Mk99ezVdC4HhNWK=Ea83Ps-qaQq=_-fzVoWZ8sYQ@mail.gmail.com' \
    --to=ilias.apalodimas@linaro.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=liangchen.linux@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=linyunsheng@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox