From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH v3 0/2] Fix file locking in EAL memory
Date: Fri, 27 Apr 2018 23:50:16 +0200 [thread overview]
Message-ID: <4395515.ft7v3IFq35@xps> (raw)
In-Reply-To: <cover.1524652577.git.anatoly.burakov@intel.com>
> Anatoly Burakov (2):
> mem: add memalloc init stage
> mem: revert to using flock() and add per-segment lockfiles
Applied, thanks
next prev parent reply other threads:[~2018-04-27 21:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 12:26 [dpdk-dev] [PATCH " Anatoly Burakov
2018-04-19 12:26 ` [dpdk-dev] [PATCH 1/2] mem: add memalloc init stage Anatoly Burakov
2018-04-24 14:06 ` Bruce Richardson
2018-04-19 12:26 ` [dpdk-dev] [PATCH 2/2] mem: revert to using flock() and add per-segment lockfiles Anatoly Burakov
2018-04-24 13:57 ` Bruce Richardson
2018-04-24 14:07 ` Bruce Richardson
2018-04-24 15:54 ` [dpdk-dev] [PATCH v2 0/2] Fix file locking in EAL memory Anatoly Burakov
2018-04-24 16:32 ` Stephen Hemminger
2018-04-24 17:25 ` Burakov, Anatoly
2018-04-24 20:05 ` Thomas Monjalon
2018-04-24 20:34 ` Stephen Hemminger
2018-04-25 10:36 ` [dpdk-dev] [PATCH v3 " Anatoly Burakov
2018-04-27 21:50 ` Thomas Monjalon [this message]
2018-04-25 10:36 ` [dpdk-dev] [PATCH v3 1/2] mem: add memalloc init stage Anatoly Burakov
2018-04-25 10:36 ` [dpdk-dev] [PATCH v3 2/2] mem: revert to using flock() and add per-segment lockfiles Anatoly Burakov
2018-04-28 9:38 ` Andrew Rybchenko
2018-04-30 8:29 ` Burakov, Anatoly
2018-04-30 11:31 ` Burakov, Anatoly
2018-04-30 11:51 ` Maxime Coquelin
2018-04-30 13:08 ` Andrew Rybchenko
2018-04-24 15:54 ` [dpdk-dev] [PATCH v2 1/2] mem: add memalloc init stage Anatoly Burakov
2018-04-24 15:54 ` [dpdk-dev] [PATCH v2 2/2] mem: revert to using flock() and add per-segment lockfiles Anatoly Burakov
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=4395515.ft7v3IFq35@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@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).