From: Andrew Rybchenko <arybchenko@solarflare.com>
To: "Sachin Saxena (OSS)" <sachin.saxena@oss.nxp.com>, <dev@dpdk.org>
Cc: <thomas@monjalon.net>, Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v1] mempool: dump socket id attribute
Date: Fri, 11 Sep 2020 11:31:31 +0300 [thread overview]
Message-ID: <51f75e35-88ba-c88d-ba36-7a5bbac8e41e@solarflare.com> (raw)
In-Reply-To: <20200911081316.6278-1-sachin.saxena@oss.nxp.com>
On 9/11/20 11:13 AM, Sachin Saxena (OSS) wrote:
> From: Sachin Saxena <sachin.saxena@oss.nxp.com>
>
> Enhance the dump function to also print socket_id attribute
> passed at creation time.
>
> Signed-off-by: Sachin Saxena <sachin.saxena@oss.nxp.com>
Please, include maintainers in the recipient list the next time.
Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
> ---
> lib/librte_mempool/rte_mempool.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/librte_mempool/rte_mempool.c b/lib/librte_mempool/rte_mempool.c
> index 7774f0c8d..2d49ecd2b 100644
> --- a/lib/librte_mempool/rte_mempool.c
> +++ b/lib/librte_mempool/rte_mempool.c
> @@ -1275,6 +1275,7 @@ rte_mempool_dump(FILE *f, struct rte_mempool *mp)
>
> fprintf(f, "mempool <%s>@%p\n", mp->name, mp);
> fprintf(f, " flags=%x\n", mp->flags);
> + fprintf(f, " socket_id=%d\n", mp->socket_id);
> fprintf(f, " pool=%p\n", mp->pool_data);
> fprintf(f, " iova=0x%" PRIx64 "\n", mp->mz->iova);
> fprintf(f, " nb_mem_chunks=%u\n", mp->nb_mem_chunks);
>
next prev parent reply other threads:[~2020-09-11 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 8:13 Sachin Saxena (OSS)
2020-09-11 8:31 ` Andrew Rybchenko [this message]
2020-10-05 22:57 ` Thomas Monjalon
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=51f75e35-88ba-c88d-ba36-7a5bbac8e41e@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).