From: Peter Zijlstra <peterz@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Sasha Levin <levinsasha928@gmail.com>,
Wu Fengguang <fengguang.wu@intel.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] block: Convert BDI proportion calculations to flexible proportions
Date: Fri, 01 Jun 2012 12:13:58 +0200 [thread overview]
Message-ID: <1338545638.28384.137.camel@twins> (raw)
In-Reply-To: <20120531224206.GC19050@quack.suse.cz>
On Fri, 2012-06-01 at 00:42 +0200, Jan Kara wrote:
> On Fri 01-06-12 00:26:05, Peter Zijlstra wrote:
> > On Fri, 2012-06-01 at 00:11 +0200, Jan Kara wrote:
> > > bool fprop_new_period(struct fprop_global *p, int periods)
> > > {
> > > - u64 events = percpu_counter_sum(&p->events);
> > > + u64 events;
> > > + unsigned long flags;
> > >
> > > + local_irq_save(flags);
> > > + events = percpu_counter_sum(&p->events);
> > > + local_irq_restore(flags);
> > > /*
> > > * Don't do anything if there are no events.
> > > */
> > > @@ -73,7 +77,9 @@ bool fprop_new_period(struct fprop_global *p, int periods)
> > > if (periods < 64)
> > > events -= events >> periods;
> > > /* Use addition to avoid losing events happening between sum and set */
> > > + local_irq_save(flags);
> > > percpu_counter_add(&p->events, -events);
> > > + local_irq_restore(flags);
> > > p->period += periods;
> > > write_seqcount_end(&p->sequence);
> >
> > Uhm, why bother enabling it in between? Just wrap the whole function in
> > a single IRQ disable.
> I wanted to have interrupts disabled for as short as possible but if you
> think it doesn't matter, I'll take your advice. The result is attached.
Thing is, disabling interrupts is quite expensive and the extra few
instructions covered isn't much.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-06-01 10:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 16:59 [PATCH 0/2 v4] Flexible proportions Jan Kara
2012-05-24 16:59 ` [PATCH 1/2] lib: Proportions with flexible period Jan Kara
2012-05-24 16:59 ` [PATCH 2/2] block: Convert BDI proportion calculations to flexible proportions Jan Kara
2012-05-28 15:49 ` Sasha Levin
2012-05-29 12:34 ` Jan Kara
2012-05-29 12:38 ` Peter Zijlstra
2012-05-29 12:54 ` Jan Kara
2012-05-31 22:11 ` Jan Kara
2012-05-31 22:26 ` Peter Zijlstra
2012-05-31 22:42 ` Jan Kara
2012-06-01 3:10 ` Fengguang Wu
2012-06-01 10:13 ` Peter Zijlstra [this message]
2012-05-25 9:12 ` [PATCH 0/2 v4] Flexible proportions Peter Zijlstra
2012-05-25 9:29 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2012-05-15 15:43 [PATCH 0/2 v3] " Jan Kara
2012-05-15 15:43 ` [PATCH 2/2] block: Convert BDI proportion calculations to flexible proportions Jan Kara
2012-05-17 22:04 ` Peter Zijlstra
2012-05-18 14:24 ` Jan Kara
2012-05-18 14:34 ` Peter Zijlstra
2012-05-03 22:39 [PATCH 0/2 v2] Flexible proportions for BDIs Jan Kara
2012-05-03 22:39 ` [PATCH 2/2] block: Convert BDI proportion calculations to flexible proportions Jan Kara
2012-05-07 14:47 ` Fengguang Wu
2012-05-07 15:21 ` Peter Zijlstra
2012-05-09 11:38 ` Jan Kara
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=1338545638.28384.137.camel@twins \
--to=peterz@infradead.org \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).