All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Joe Thornber <thornber@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: [PATCH 1/2] dm-kcopyd: introduce per-module throttle structure
Date: Fri, 10 Jun 2011 09:41:50 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.1106100937430.32120@hs20-bc2-1.build.redhat.com> (raw)
In-Reply-To: <20110610101446.GB10144@ubuntu>



On Fri, 10 Jun 2011, Joe Thornber wrote:

> On Fri, Jun 10, 2011 at 11:28:34AM +0200, Lars Ellenberg wrote:
> > On Fri, Jun 10, 2011 at 09:44:25AM +0100, Joe Thornber wrote:
> > > On Thu, Jun 09, 2011 at 12:08:08PM -0400, Mikulas Patocka wrote:
> > > > 
> > > > 
> > > > On Thu, 9 Jun 2011, Joe Thornber wrote:
> > > > > What we're trying to do is avoid kcopyd issuing so much io that it
> > > > > interferes with userland io.
> > > > 
> > > > But you don't know if there is some userland IO or not to the same disk.
> > > 
> > > None the less, this was the motivation Alasdair gave for wanting this
> > > throttling.
> > 
> > Not sure if it helps,
> > but are you familiar with the MD raid rebuild throttling?
> 
> Lars,
> 
> This is very helpful, thankyou.  Any thoughts on this Mikulas?
> 
> - Joe

This works if the data is directly on the partition, but it won't work on 
the device mapper (if MD is on the device mapper, it won't work too).

The device mapper has no function to tell where the bio is finally 
remapped, so you can't read disk statistics for that particular disk.

Mikulas

  reply	other threads:[~2011-06-10 13:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 22:03 [PATCH 1/2] dm-kcopyd: introduce per-module throttle structure Mikulas Patocka
2011-06-01  6:18 ` Ankit Jain
2011-06-01  7:13   ` Ankit Jain
2011-06-02 19:16   ` Mikulas Patocka
2011-06-01  9:51 ` Joe Thornber
2011-06-02 19:55   ` Mikulas Patocka
2011-06-03 11:01     ` Joe Thornber
2011-06-03 15:54       ` Mike Snitzer
2011-06-07 17:50       ` Mikulas Patocka
2011-06-09  9:47         ` Joe Thornber
2011-06-09 16:08           ` Mikulas Patocka
2011-06-09 16:27             ` Alasdair G Kergon
2011-06-10  8:44             ` Joe Thornber
2011-06-10  9:28               ` Lars Ellenberg
2011-06-10 10:14                 ` Joe Thornber
2011-06-10 13:41                   ` Mikulas Patocka [this message]
2011-06-10 13:48                     ` Joe Thornber
2011-06-10 16:13                       ` Lars Ellenberg
2011-06-10 13:51                     ` Mike Snitzer
2011-06-11 20:27               ` Mikulas Patocka
2011-06-13  9:17                 ` Joe Thornber
2011-06-13 21:06                   ` Mikulas Patocka
2011-06-14  8:34                     ` Joe Thornber

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=Pine.LNX.4.64.1106100937430.32120@hs20-bc2-1.build.redhat.com \
    --to=mpatocka@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=thornber@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.