mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: Mike Galbraith <efault@gmx.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: get/put_cpu() usage in block/blk-mq.c
Date: Tue, 9 May 2017 10:32:38 -0600	[thread overview]
Message-ID: <1c0ec340-675f-152f-aa4f-37b6d0c0734e@fb.com> (raw)
In-Reply-To: <1494347203.4440.24.camel@gmx.de>

On 05/09/2017 10:26 AM, Mike Galbraith wrote:
> On Tue, 2017-05-09 at 09:45 -0600, Jens Axboe wrote:
> 
>>>>>>> Is it from this_cpu_ptr() in blk_stat_add()?
>>>>>>
>>>>>> Yeah.
>>>>>
>>>>> So why is this complaining, doesn't rcu_read_lock() disable
>>>>> preemption?
>>>>
>>>> Ah, I guess it doesn't if PREEMPT_RCU is set. How about the
>>>> below?
>>>
>>> Should do it.  I was about to run LTP (where it turned up) again
>>> anyway, I'll add this.  No news is good news, what you should hear.
>>
>> Thanks, let me know, so I can add your tested-by (or whatever you
>> prefer).
> 
> Sure, but s/get_cpu_var/get_cpu_ptr first.

Doh.

diff --git a/block/blk-stat.c b/block/blk-stat.c
index 6c2f40940439..c52356d90fe3 100644
--- a/block/blk-stat.c
+++ b/block/blk-stat.c
@@ -96,13 +96,16 @@ void blk_stat_add(struct request *rq)
 
 	rcu_read_lock();
 	list_for_each_entry_rcu(cb, &q->stats->callbacks, list) {
-		if (blk_stat_is_active(cb)) {
-			bucket = cb->bucket_fn(rq);
-			if (bucket < 0)
-				continue;
-			stat = &this_cpu_ptr(cb->cpu_stat)[bucket];
-			__blk_stat_add(stat, value);
-		}
+		if (!blk_stat_is_active(cb))
+			continue;
+
+		bucket = cb->bucket_fn(rq);
+		if (bucket < 0)
+			continue;
+
+		stat = &get_cpu_ptr(cb->cpu_stat)[bucket];
+		__blk_stat_add(stat, value);
+		put_cpu_ptr(cb->cpu_stat);
 	}
 	rcu_read_unlock();
 }

-- 
Jens Axboe

  reply	other threads:[~2017-05-09 16:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09  6:07 Mike Galbraith
2017-05-09 14:53 ` Jens Axboe
2017-05-09 15:04   ` Mike Galbraith
2017-05-09 15:13     ` Jens Axboe
2017-05-09 15:15       ` Jens Axboe
2017-05-09 15:40         ` Mike Galbraith
2017-05-09 15:45           ` Jens Axboe
2017-05-09 16:26             ` Mike Galbraith
2017-05-09 16:32               ` Jens Axboe [this message]
2017-05-09 16:52                 ` Mike Galbraith

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=1c0ec340-675f-152f-aa4f-37b6d0c0734e@fb.com \
    --to=axboe@fb.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®