From: Liang Chen <liangchen.linux@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
hawk@kernel.org, linyunsheng@huawei.com, netdev@vger.kernel.org,
linux-mm@kvack.org, jasowang@redhat.com, almasrymina@google.com
Subject: Re: [PATCH net-next v8 4/4] skbuff: Optimization of SKB coalescing for page pool
Date: Thu, 14 Dec 2023 10:46:34 +0800 [thread overview]
Message-ID: <CAKhg4t+_zn4EieUf__Baivnox-soMGKV=g+fPeFWL9zVR6x1ww@mail.gmail.com> (raw)
In-Reply-To: <20231213183420.78b3be68@kernel.org>
On Thu, Dec 14, 2023 at 10:34 AM Jakub Kicinski <kuba@kernel.org> wrote:
>
> On Thu, 14 Dec 2023 10:26:47 +0800 Liang Chen wrote:
> > If there is no objection, it will be included in v10.
>
> If I manage to reach you before you post - please hold off for another
> 30min with posting, I'm going to apply patch 1.
Sure. Thank you!
prev parent reply other threads:[~2023-12-14 2:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 3:52 [PATCH net-next v8 0/4] skbuff: Optimize " Liang Chen
2023-12-11 3:52 ` [PATCH net-next v8 1/4] page_pool: transition to reference count management after page draining Liang Chen
2023-12-11 7:43 ` Ilias Apalodimas
2023-12-11 3:52 ` [PATCH net-next v8 2/4] page_pool: halve BIAS_MAX for multiple user references of a fragment Liang Chen
2023-12-11 10:12 ` Jesper Dangaard Brouer
2023-12-11 3:52 ` [PATCH net-next v8 3/4] skbuff: Add a function to check if a page belongs to page_pool Liang Chen
2023-12-11 7:40 ` Ilias Apalodimas
2023-12-11 3:52 ` [PATCH net-next v8 4/4] skbuff: Optimization of SKB coalescing for page pool Liang Chen
2023-12-11 7:46 ` Ilias Apalodimas
2023-12-11 20:14 ` Jakub Kicinski
2023-12-12 3:00 ` Liang Chen
2023-12-13 7:09 ` Ilias Apalodimas
2023-12-14 2:26 ` Liang Chen
2023-12-14 2:34 ` Jakub Kicinski
2023-12-14 2:46 ` Liang Chen [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='CAKhg4t+_zn4EieUf__Baivnox-soMGKV=g+fPeFWL9zVR6x1ww@mail.gmail.com' \
--to=liangchen.linux@gmail.com \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--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