From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/3] mem: provide thread-unsafe contig walk variant
Date: Fri, 13 Jul 2018 11:21:04 +0200 [thread overview]
Message-ID: <4613648.bFHoFLOs9j@xps> (raw)
In-Reply-To: <a033d2f5109529a159d85c58d7b101b5a6dadacf.1528796062.git.anatoly.burakov@intel.com>
12/06/2018 11:46, Anatoly Burakov:
> Sometimes, user code needs to walk memseg list while being inside
> a memory-related callback. Rather than making everyone copy around
> the same iteration code and depending on DPDK internals, provide an
> official way to do memseg_contig_walk() inside callbacks.
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Series applied, thanks
prev parent reply other threads:[~2018-07-13 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 9:46 Anatoly Burakov
2018-06-12 9:46 ` [dpdk-dev] [PATCH 2/3] mem: provide thread-unsafe memseg " Anatoly Burakov
2018-06-12 9:46 ` [dpdk-dev] [PATCH 3/3] mem: provide thread-unsafe memseg list " Anatoly Burakov
2018-07-13 9:21 ` Thomas Monjalon [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=4613648.bFHoFLOs9j@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.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 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).