From: David Marchand <david.marchand@redhat.com>
To: Owen Hilyard <ohilyard@iol.unh.edu>
Cc: dev <dev@dpdk.org>, dpdklab <dpdklab@iol.unh.edu>,
Gaetan Rivet <grive@u256.net>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-dev] Memory leak in rte_pci_scan
Date: Tue, 15 Jun 2021 09:43:05 +0200 [thread overview]
Message-ID: <CAJFAV8y2Dk0QqRV9yUrrbTw6nmXvixkQoX-wzZxvmOMnHcY8_w@mail.gmail.com> (raw)
In-Reply-To: <CAHx6DYBqef4kFn1_v9XDnbsFHeacgUmqS1mqjZvCnQuzf3Zunw@mail.gmail.com>
Hi Owen,
On Mon, Jun 14, 2021 at 10:42 PM Owen Hilyard <ohilyard@iol.unh.edu> wrote:
>
> From what I've seen so far, that fixes the PCI leak. That just leaves a few other places. I'll try to get the complete list to you tomorrow, since running the full set of unit tests takes quite a few hours when ASAN is involved.
Ok, thanks for the test.
I'll send a patch on the pci bus.
Just odd that it tooks hours in your case.
On my f32 system, it took 3/4 minutes.
It is probably worth looking why the difference.
We can't have asan enabled at UNH otherwise.
--
David Marchand
next prev parent reply other threads:[~2021-06-15 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 18:47 [dpdk-dev] Memory leak in rte_pci_scan Owen Hilyard
2021-06-14 9:11 ` David Marchand
2021-06-14 10:30 ` David Marchand
2021-06-14 20:41 ` Owen Hilyard
2021-06-15 7:43 ` David Marchand [this message]
2021-06-15 15:15 ` Owen Hilyard
2021-06-16 9:37 ` David Marchand
[not found] ` <CAHx6DYAADd4b9U8m7hNk0d_KkxgYuLF7_ntf+q57tE39W0H2bQ@mail.gmail.com>
2021-06-16 17:40 ` David Marchand
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=CAJFAV8y2Dk0QqRV9yUrrbTw6nmXvixkQoX-wzZxvmOMnHcY8_w@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=grive@u256.net \
--cc=jerinj@marvell.com \
--cc=ohilyard@iol.unh.edu \
/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.