public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: righi.andrea@gmail.com
Cc: axboe@kernel.dk, containers@lists.linux-foundation.org,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Paul Menage <menage@google.com>,
	Carl Henrik Lunde <chlunde@ping.uio.no>,
	matt@bluehost.com, roberto@unbit.it,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	Divyesh Shah <dpshah@google.com>
Subject: Re: [PATCH 1/3] i/o bandwidth controller documentation
Date: Sun, 22 Jun 2008 11:03:43 -0500 (CDT)	[thread overview]
Message-ID: <17241648.1214150623059.JavaMail.oracle@acsmt302.oracle.com> (raw)
In-Reply-To: <485CD956.3070209@gmail.com>

--- Original Message ---
> Thanks Randy, I've applied all your fixes to my local
> documentation,
> next patchset version will include them. A few small comments
> below.
> 
> >> +WARNING: per-block device limiting rules always refer to the dev_t device
> >> +number. If a block device is unplugged (i.e. a USB device) the limiting rules
> >> +associated to that device persist and they are still valid if a new device is
> > 
> > associated with (?)
> 
> what about:
> 
> ...the limiting rules defined for that device...

Hi Andrea,

Yes, that's fine.

Thanks.


  reply	other threads:[~2008-06-22 16:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20 10:05 [PATCH 1/3] i/o bandwidth controller documentation Andrea Righi
2008-06-20 17:08 ` Randy Dunlap
2008-06-21 10:35   ` Andrea Righi
2008-06-22 16:03     ` Randy Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-04 13:58 Andrea Righi
     [not found] <200806201602.m5KG2Zx32671@inv.it.uc3m.es>
2008-06-20 16:11 ` Peter T. Breuer
2008-07-04 15:35   ` Andrea Righi
2008-06-06 22:27 Andrea Righi
2008-06-11 22:42 ` Randy Dunlap
2008-06-11 22:51   ` Andrea Righi
2008-06-18 15:16 ` Carl Henrik Lunde
2008-06-18 22:28   ` Andrea Righi

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=17241648.1214150623059.JavaMail.oracle@acsmt302.oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=chlunde@ping.uio.no \
    --cc=containers@lists.linux-foundation.org \
    --cc=dpshah@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@bluehost.com \
    --cc=menage@google.com \
    --cc=righi.andrea@gmail.com \
    --cc=roberto@unbit.it \
    /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