From: Milos Vyletel <milos@redhat.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Namhyung Kim <namhyung@kernel.org>,
Milos Vyletel <milos@redhat.com>, Jiri Olsa <jolsa@kernel.org>,
He Kuang <hekuang@huawei.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org (open list:PERFORMANCE EVENT...)
Subject: [PATCH 0/2] Add perf debug dir locking
Date: Thu, 14 May 2015 09:28:09 +0200 [thread overview]
Message-ID: <1431588493-1474-1-git-send-email-milos@redhat.com> (raw)
Hi,
this series is follow up on my last submission where Jirka mentioned it would
be nice to have some locking around .debug dir operations.
https://lkml.org/lkml/2015/3/20/126
Following two patches add such functionality by utilizing flock. Since flock
supports both shared(read) and exclusive(write) locks both variants are being
added so that we can use multiple readers while only one writer.
Having said that any comments/suggestions on the code are welcome.
I did some basic testing. Mostly manual tool testing as well as the recreator
from above mentioned URL. I do not expect any functional change however more
testing is welcome.
Milos
Milos Vyletel (2):
perf/tools: add read/write buildid dir locks
perf/tools: put new buildid locks to use
tools/perf/builtin-buildid-cache.c | 12 +++++
tools/perf/util/build-id.c | 97 ++++++++++++++++++++++++++++++++++----
tools/perf/util/build-id.h | 5 ++
3 files changed, 106 insertions(+), 8 deletions(-)
--
2.4.0
next reply other threads:[~2015-05-14 7:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 7:28 Milos Vyletel [this message]
2015-05-14 7:28 ` [PATCH 1/2] perf/tools: add read/write buildid dir locks Milos Vyletel
2015-05-14 7:28 ` [PATCH 2/2] perf/tools: put new buildid locks to use Milos Vyletel
2015-05-14 10:40 ` Ingo Molnar
2015-05-14 11:38 ` Jiri Olsa
2015-05-14 15:44 ` Milos Vyletel
2015-05-14 17:38 ` Ingo Molnar
2015-05-14 17:38 ` Ingo Molnar
2015-05-20 7:27 ` Milos Vyletel
2015-06-03 11:13 ` Milos Vyletel
2015-06-03 11:21 ` Ingo Molnar
2015-06-03 11:27 ` Milos Vyletel
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=1431588493-1474-1-git-send-email-milos@redhat.com \
--to=milos@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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