From: Vivek Goyal <vgoyal@redhat.com>
To: Heinz Mauelshagen <heinzm@redhat.com>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH} dm-throttle: new device mapper target to throttle reads and writes
Date: Tue, 10 Aug 2010 14:41:38 -0400 [thread overview]
Message-ID: <20100810184138.GC9028@redhat.com> (raw)
In-Reply-To: <1281447742.4964.46.camel@o>
On Tue, Aug 10, 2010 at 03:42:22PM +0200, Heinz Mauelshagen wrote:
[..]
> +/* Decide about throttling (ie. deferring bios). */
> +static int throttle(struct throttle_c *tc, struct bio *bio)
> +{
> + int rw = (bio_data_dir(bio) == WRITE);
> + unsigned bps; /* Bytes per second. */
> +
> + smp_rmb();
> + bps = tc->params.bs[rw];
> + if (bps) {
> + unsigned size;
> + struct account *ac = &tc->account;
> + struct ac_rw *ac_rw = ac->rw + rw;
> +
> + if (time_after(jiffies, ac_rw->end_jiffies))
> + /* Measure time exceeded. */
> + account_reset(rw, tc);
> + else if (test_bit(rw, &ac->flags))
> + /* In case we're throttled already. */
> + return 1;
> +
> + /* Account I/O size. */
> + size = ac_rw->size + bio->bi_size;
> + if (size > bps) {
> + /* Hit kilobytes per second threshold. */
> + set_bit(rw, &ac->flags);
> + return 1;
If bio->bi_size is greate than bps, will I always keep on throttling
and hang?
[..]
> +/* Map a throttle io. */
> +static int throttle_map(struct dm_target *ti, struct bio *bio,
> + union map_info *map_context)
> +{
> + int r, rw = (bio_data_dir(bio) == WRITE);
> + struct throttle_c *tc = ti->private;
> + struct ac_rw *ac_rw = tc->account.rw + rw;
> +
> + mutex_lock(&ac_rw->mutex);
> + do {
> + r = throttle(tc, bio);
> + if (r) {
> + long end = ac_rw->end_jiffies, j = jiffies;
> +
> + /* Wait till next second when KB/s reached. */
> + if (j < end)
> + schedule_timeout_uninterruptible(end - j);
> + }
So a thread is blocked if it crossed the IO rate. There is no such mechanism
to take the bio, statsh away somewhere and dispatch it to disk later. The
way request queue descriptors work. Processes are blocked only if queue
is congested otherwise one allows processes to submit requests and go
back and do other work.
I am assuming that this will be bad for AIO.
Thanks
Vivek
next prev parent reply other threads:[~2010-08-10 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 13:42 [PATCH} dm-throttle: new device mapper target to throttle reads and writes Heinz Mauelshagen
2010-08-10 14:44 ` Vivek Goyal
2010-08-12 9:08 ` Heinz Mauelshagen
2010-08-12 16:46 ` Vivek Goyal
2010-08-12 20:32 ` Vivek Goyal
2010-08-13 11:19 ` Heinz Mauelshagen
2010-08-10 18:41 ` Vivek Goyal [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-11 15:45 [PATCH] " Heinz Mauelshagen
2010-08-12 14:23 ` Vivek Goyal
2010-08-12 21:23 ` Heinz Mauelshagen
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=20100810184138.GC9028@redhat.com \
--to=vgoyal@redhat.com \
--cc=dm-devel@redhat.com \
--cc=heinzm@redhat.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;
as well as URLs for NNTP newsgroup(s).