From: Jesper Dangaard Brouer <brouer@redhat.com>
To: "Jonathan Lemon" <jonathan.lemon@gmail.com>
Cc: "Alexei Starovoitov" <ast@fb.com>,
netdev@vger.kernel.org, davem@davemloft.net,
"Kernel Team" <Kernel-team@fb.com>,
ilias.apalodimas@linaro.org, brouer@redhat.com,
Brendan Gregg <brendan.d.gregg@gmail.com>
Subject: Re: [net-next PATCH] page_pool: do not release pool until inflight == 0.
Date: Wed, 13 Nov 2019 17:37:12 +0100 [thread overview]
Message-ID: <20191113173712.173a1813@carbon> (raw)
In-Reply-To: <20191113110823.0e1186a5@carbon>
On Wed, 13 Nov 2019 11:08:23 +0100
Jesper Dangaard Brouer <brouer@redhat.com> wrote:
> The basic idea is to use these tracepoints to detect if we leak
> DMA-mappings. I'll try write the bpftrace script today, and
> see it I can live without the counter.
Didn't finish, here is how far I got:
https://github.com/xdp-project/xdp-project/blob/master/areas/mem/bpftrace/page_pool_track_leaks01.bt
In the end of the bpftrace script, I needed to iterate over a map,
which I don't think bpftrace supports (Brendan) ?
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2019-11-13 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 5:32 [net-next PATCH] page_pool: do not release pool until inflight == 0 Jonathan Lemon
2019-11-12 12:08 ` Jesper Dangaard Brouer
2019-11-12 16:33 ` Jonathan Lemon
2019-11-12 16:48 ` Jesper Dangaard Brouer
2019-11-12 17:14 ` Jonathan Lemon
2019-11-12 17:23 ` Alexei Starovoitov
2019-11-12 17:32 ` Jonathan Lemon
2019-11-13 10:08 ` Jesper Dangaard Brouer
2019-11-13 16:37 ` Jesper Dangaard Brouer [this message]
2019-11-12 15:11 ` Jesper Dangaard Brouer
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=20191113173712.173a1813@carbon \
--to=brouer@redhat.com \
--cc=Kernel-team@fb.com \
--cc=ast@fb.com \
--cc=brendan.d.gregg@gmail.com \
--cc=davem@davemloft.net \
--cc=ilias.apalodimas@linaro.org \
--cc=jonathan.lemon@gmail.com \
--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.