From: Vivek Goyal <vgoyal@redhat.com>
To: Wanlong Gao <gaowanlong@cn.fujitsu.com>
Cc: menage@google.com, lizf@cn.fujitsu.com, axboe@kernel.dk,
linux-kernel@vger.kernel.org, wanlong.gao@gmail.com
Subject: Re: [PATCH v3] blk-cgroup:be able to remove the record of unplugged device
Date: Tue, 26 Jul 2011 10:44:27 -0400 [thread overview]
Message-ID: <20110726144427.GB13780@redhat.com> (raw)
In-Reply-To: <1311645400-19434-1-git-send-email-gaowanlong@cn.fujitsu.com>
On Tue, Jul 26, 2011 at 09:56:40AM +0800, Wanlong Gao wrote:
>
> Write a record like:
> echo 8:0 1000 > blkio.throttle.read_bps_device
> to control the bps of the device.
> And then unplug this device without doing
> "8:0 0 > blkio.throttle.read_bps_device" to remove the record,
> it will not be removed until reboot, because if the device is removed,
> write some record will return "-ENODEV".
>
> With this patch, when the device is removed, then if we want to remove
> the record for this removed device, just write "0" then it'll not check
> if it is a present device, just remove the present record.
Ok, not checking for device presence while deleting a rule makes sense.
Some comments inline.
[..]
>
> Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
> ---
> block/blk-cgroup.c | 18 +++++++++---------
> 1 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c
> index bcaf16e..246645c 100644
> --- a/block/blk-cgroup.c
> +++ b/block/blk-cgroup.c
> @@ -785,7 +785,7 @@ static int blkio_policy_parse_and_set(char *buf,
> {
> char *s[4], *p, *major_s = NULL, *minor_s = NULL;
> int ret;
> - unsigned long major, minor, temp;
> + unsigned long major, minor, weight;
Do not replace temp with name weight. The place you are parsing it,
it could be weight, bps or iops. So lets keep the generic name in
place.
> int i = 0;
> dev_t dev;
> u64 bps, iops;
> @@ -826,25 +826,25 @@ static int blkio_policy_parse_and_set(char *buf,
>
> dev = MKDEV(major, minor);
>
> - ret = blkio_check_dev_num(dev);
> + ret = strict_strtoul(s[1], 10, &weight);
> if (ret)
> + return -EINVAL;
> +
> + ret = blkio_check_dev_num(dev);
> + if (ret && (weight != 0))
> return ret;
Can you simplify above and just put a one comment also. Don't even call
blkio_check_dev_num() if we are removing the rule.
/* For rule removal, do not check for device presence. */
if (temp != 0)
ret = blkio_check_dev_num(dev);
Thanks
Vivek
next prev parent reply other threads:[~2011-07-26 14:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 6:03 [PATCH] cgroup:be able to remove the record of unplugged device Wanlong Gao
2011-07-25 20:45 ` Paul Menage
2011-07-26 0:37 ` [PATCH v2] " Wanlong Gao
2011-07-26 1:29 ` Paul Menage
2011-07-26 1:56 ` [PATCH v3] blk-cgroup:be " Wanlong Gao
2011-07-26 2:23 ` Li Zefan
2011-07-26 3:00 ` [PATCH v4] " Wanlong Gao
2011-07-26 14:44 ` Vivek Goyal [this message]
2011-07-26 14:59 ` [PATCH v3] " Wanlong Gao
2011-07-26 17:17 ` Paul Menage
2011-07-26 17:41 ` Vivek Goyal
2011-07-26 18:40 ` Paul Menage
2011-07-26 19:24 ` Vivek Goyal
2011-07-27 0:11 ` [PATCH v5] " Wanlong Gao
2011-07-27 14:11 ` Vivek Goyal
2011-08-17 12:57 ` Wanlong Gao
2011-08-17 14:18 ` Vivek Goyal
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=20110726144427.GB13780@redhat.com \
--to=vgoyal@redhat.com \
--cc=axboe@kernel.dk \
--cc=gaowanlong@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=wanlong.gao@gmail.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.