From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: acme@redhat.com, kstewart@linuxfoundation.org,
tglx@linutronix.de, pombredanne@nexb.com,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org, uneedsihyeon@gmail.com,
kjlx@templeofstupid.com,
ravi Bangoria <ravi.bangoria@linux.ibm.com>
Subject: Re: [PATCH 3/3] perf/buildid-cache: Support --purge-all option
Date: Mon, 16 Apr 2018 15:10:40 +0530 [thread overview]
Message-ID: <f921f16f-578a-955c-4301-e596adbdcd4b@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180416182735.4399e94b3c7e6d190ec7dc3e@kernel.org>
Hi Masami,
On 04/16/2018 02:57 PM, Masami Hiramatsu wrote:
> On Mon, 9 Apr 2018 16:36:33 +0530
> Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com> wrote:
>
>> User can remove files from cache using --remove/--purge options
>> but both needs list of files as an argument. It's not convenient
>> when you want to flush out entire cache. Add an option to purge
>> all files from cache.
>>
>> Ex,
>> # perf buildid-cache -l
>> /tmp/a.out (8a86ef73e44067bca52cc3f6cd3e5446c783391c)
>> /tmp/a.out.1 (ebe71fdcf4b366518cc154d570a33cd461a51c36)
>> # perf buildid-cache -P -v
>> Removing /tmp/a.out (8a86ef73e44067bca52cc3f6cd3e5446c783391c): Ok
>> Removing /tmp/a.out.1 (ebe71fdcf4b366518cc154d570a33cd461a51c36): Ok
>> Purged all: Ok
> Hmm, for purging all caches will be done by
>
> $ rm -rf ~/.debug
>
> Are there any difference?
No logical difference if you know it's ~/.debug where it goes. :)
I also used to do rm -rf earlier.
This option is for a perf users. But I'm fine if it's not really needed.
Will drop it.
Thanks,
Ravi
next prev parent reply other threads:[~2018-04-16 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 11:06 [PATCH 0/3] perf/buildid-cache: Add --list and --purge-all options Ravi Bangoria
2018-04-09 11:06 ` [PATCH 1/3] tools/parse-options: Add '\n' at the end of error messages Ravi Bangoria
2018-04-16 9:25 ` Masami Hiramatsu
2018-04-09 11:06 ` [PATCH 2/3] perf/buildid-cache: Support --list option Ravi Bangoria
2018-04-13 12:55 ` Jiri Olsa
2018-04-13 12:55 ` Jiri Olsa
2018-04-13 12:58 ` Jiri Olsa
2018-04-16 6:57 ` Ravi Bangoria
2018-04-09 11:06 ` [PATCH 3/3] perf/buildid-cache: Support --purge-all option Ravi Bangoria
2018-04-16 9:27 ` Masami Hiramatsu
2018-04-16 9:40 ` Ravi Bangoria [this message]
2018-04-16 10:30 ` Jiri Olsa
2018-04-18 5:53 ` Masami Hiramatsu
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=f921f16f-578a-955c-4301-e596adbdcd4b@linux.vnet.ibm.com \
--to=ravi.bangoria@linux.vnet.ibm.com \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=kjlx@templeofstupid.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=pombredanne@nexb.com \
--cc=ravi.bangoria@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=uneedsihyeon@gmail.com \
/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
Powered by JetHome