From: Jens Axboe <axboe@kernel.dk>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Reshetova, Elena" <elena.reshetova@intel.com>,
Eric Biggers <ebiggers3@gmail.com>,
Kees Cook <keescook@chromium.org>,
Christoph Hellwig <hch@infradead.org>,
"james.bottomley@hansenpartnership.com"
<james.bottomley@hansenpartnership.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"fujita.tomonori@lab.ntt.co.jp" <fujita.tomonori@lab.ntt.co.jp>,
"mingo@redhat.com" <mingo@redhat.com>, "clm@fb.com" <clm@fb.com>,
"jbacik@fb.com" <jbacik@fb.com>,
"dsterba@suse.com" <dsterba@suse.com>
Subject: Re: [PATCH 0/5] v2: block subsystem refcounter conversions
Date: Fri, 21 Apr 2017 10:29:45 -0600 [thread overview]
Message-ID: <99e3518a-bb1a-cab2-80b8-dd466827b5e6@kernel.dk> (raw)
In-Reply-To: <20170421152241.q45w3ckjax5xiddq@hirez.programming.kicks-ass.net>
On 04/21/2017 09:22 AM, Peter Zijlstra wrote:
> On Fri, Apr 21, 2017 at 08:03:13AM -0600, Jens Axboe wrote:
>> You have it so easy - the code is completely standalone, building a
>> small test framework around it and measuring performance in _user space_
>> is trivial.
>
> Something like this you mean:
>
> https://lkml.kernel.org/r/20170322165144.dtidvvbxey7w5pbd@hirez.programming.kicks-ass.net
Yes, exactly. But it'd be great to see better coverage of the API, and
various cases of X threads running operations on the same refcount,
so we get a full view of that side too. The above looks like just
counting cycles for a single op of foo_inc().
--
Jens Axboe
next prev parent reply other threads:[~2017-04-21 16:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 11:27 Elena Reshetova
2017-04-20 11:27 ` [PATCH 1/5] block: convert bio.__bi_cnt from atomic_t to refcount_t Elena Reshetova
2017-04-20 11:27 ` [PATCH 2/5] block: convert blk_queue_tag.refcnt " Elena Reshetova
2017-04-20 11:27 ` [PATCH 3/5] block: convert blkcg_gq.refcnt " Elena Reshetova
2017-04-20 11:27 ` [PATCH 4/5] block: convert io_context.active_ref " Elena Reshetova
2017-04-20 11:27 ` [PATCH 5/5] block: convert bsg_device.ref_count " Elena Reshetova
2017-04-20 13:56 ` [PATCH 0/5] v2: block subsystem refcounter conversions Christoph Hellwig
2017-04-20 16:10 ` Reshetova, Elena
2017-04-20 18:33 ` Eric Biggers
2017-04-21 10:55 ` Reshetova, Elena
2017-04-21 14:03 ` Jens Axboe
2017-04-21 15:22 ` Peter Zijlstra
2017-04-21 16:29 ` Jens Axboe [this message]
2017-04-21 17:11 ` Kees Cook
2017-04-21 19:55 ` Eric Biggers
2017-04-21 20:22 ` Kees Cook
2017-04-21 21:27 ` James Bottomley
2017-04-21 21:30 ` Kees Cook
2017-04-21 22:01 ` James Bottomley
2017-04-21 10:56 ` Christoph Hellwig
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=99e3518a-bb1a-cab2-80b8-dd466827b5e6@kernel.dk \
--to=axboe@kernel.dk \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=ebiggers3@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=jbacik@fb.com \
--cc=keescook@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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
Powered by JetHome