From: Yunsheng Lin <linyunsheng@huawei.com>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Cc: <brouer@redhat.com>, <davem@davemloft.net>, <kuba@kernel.org>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>
Subject: Re: [PATCH net] page_pool: fix inconsistency for page_pool_ring_[un]lock()
Date: Tue, 23 May 2023 16:16:58 +0800 [thread overview]
Message-ID: <c475a980-50fb-e966-80a0-d9ccca9435d4@huawei.com> (raw)
In-Reply-To: <c6c44d10-d283-7a26-8597-6be6e29bc832@redhat.com>
On 2023/5/23 15:08, Jesper Dangaard Brouer wrote:
> On 23/05/2023 04.13, Yunsheng Lin wrote:
>> Do you still working on optimizing the page_pool destroy
>> process? If not, do you mind if I carry it on based on
>> that?
>
> I'm still working on improving the page_pool destroy process.
> I prefer to do the implementation myself.
Sure, let me know if you want a hand for that.
>
> I've not submitted another version, because I'm currently using the
> workqueue to detect/track a memory leak in mlx5.
>
> The mlx5 driver combined with XDP redirect is leaking memory, and will
> eventually lead to OOM. The workqueue warning doesn't point to the
> actual problem, but it makes is easier to notice that there is a problem.
>
> --Jesper
>
> .
>
next prev parent reply other threads:[~2023-05-23 8:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 3:17 Yunsheng Lin
2023-05-22 11:08 ` Jesper Dangaard Brouer
2023-05-22 11:45 ` Ilias Apalodimas
2023-05-23 2:13 ` Yunsheng Lin
2023-05-23 2:22 ` Jakub Kicinski
2023-05-23 2:34 ` Yunsheng Lin
2023-05-23 7:08 ` Jesper Dangaard Brouer
2023-05-23 8:16 ` Yunsheng Lin [this message]
2023-05-24 3:40 ` patchwork-bot+netdevbpf
2023-05-26 19:34 ` Jakub Kicinski
2023-05-27 7:56 ` Yunsheng Lin
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=c475a980-50fb-e966-80a0-d9ccca9435d4@huawei.com \
--to=linyunsheng@huawei.com \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jbrouer@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--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
all inboxes | Powered by JetHome®