public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Zumeng <zumeng.chen@windriver.com>
To: Ryo Tsuruta <ryov@valinux.co.jp>
Cc: agk@redhat.com, linux-kernel@vger.kernel.org,
	dm-devel@redhat.com, containers@lists.linux-foundation.org,
	virtualization@lists.linux-foundation.org,
	xen-devel@lists.xensource.com, fernando@oss.ntt.co.jp
Subject: Re: [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.8.0: Introduction
Date: Tue, 21 Oct 2008 19:10:36 +0800	[thread overview]
Message-ID: <48FDB8AC.9020707@windriver.com> (raw)
In-Reply-To: <20081017.160950.71109894.ryov@valinux.co.jp>

Hi, Ryo Tsuruta

I applied your patches(both) into the latest kernel(27), and dm-ioband
looks work well(other than schedule_timeout in alloc_ioband_device);
But I think you are the author of bio_tracking, so it is high
appreciated if you can give your comments and advices for potential
difference between 27-rc5-mm1 and 2.6.27 to me.

And our test team want to test bio_tracking as your benchmark reports,
so would you please send me your test codes? Thanks in advance.

Regards,
Zumeng

P.S. The following are my changes to avoid schedule_timeout:


diff --git a/drivers/md/dm-ioband-ctl.c b/drivers/md/dm-ioband-ctl.c
index a792620..643ca4e 100644
--- a/drivers/md/dm-ioband-ctl.c
+++ b/drivers/md/dm-ioband-ctl.c
@@ -100,6 +100,7 @@ static struct ioband_device 
*alloc_ioband_device(char *name,
                         return dp;
                 }
         }
+       spin_unlock_irqrestore(&ioband_devicelist_lock, flags);

         /*
          * Prepare its own workqueue as generic_make_request() may
@@ -133,9 +134,11 @@ static struct ioband_device 
*alloc_ioband_device(char *name,
         init_waitqueue_head(&new->g_waitq);
         init_waitqueue_head(&new->g_waitq_suspend);
         init_waitqueue_head(&new->g_waitq_flush);
-       list_add_tail(&new->g_list, &ioband_device_list);

+       spin_lock_irqsave(&ioband_devicelist_lock, flags);
+       list_add_tail(&new->g_list, &ioband_device_list);
         spin_unlock_irqrestore(&ioband_devicelist_lock, flags);
+
         return new;
  }
---

Ryo Tsuruta wrote:
> Hi Alasdair and all,
> 
> This is the dm-ioband version 1.8.0 release.
> 
> Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
> driver, which gives specified bandwidth to each job running on the same
> physical device.
> 
> This release is a minor bug fix and confirmed running on the latest
> stable kernel 2.6.27.1.
> 
> - Can be applied to the kernel 2.6.27.1 and 2.6.27-rc5-mm1.
> - Changes from 1.7.0 (posted on Oct 3, 2008):
>   - Fix a minor bug in io_limit setting that causes dm-ioband to stop
>     issuing I/O requests when a large value is set to io_limit.
> 
> Alasdair, could you please review this patch and give me any comments?
> 
> Thanks,
> Ryo Tsuruta
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  parent reply	other threads:[~2008-10-21 11:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  7:09 [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.8.0: Introduction Ryo Tsuruta
2008-10-17  7:10 ` [PATCH 1/2] dm-ioband: I/O bandwidth controller v1.8.0: Source code and patch Ryo Tsuruta
2008-10-17  7:11   ` [PATCH 2/2] dm-ioband: I/O bandwidth controller v1.8.0: Document Ryo Tsuruta
2008-10-20  8:40 ` [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.8.0: Introduction Dong-Jae Kang
2008-10-20  9:01   ` Ryo Tsuruta
2008-10-20 10:13     ` Dong-Jae Kang
2008-10-20 12:48       ` Ryo Tsuruta
2008-10-21  2:00         ` KAMEZAWA Hiroyuki
2008-10-21 11:10 ` Chen Zumeng [this message]
2008-10-22  7:55   ` Chen Zumeng
2008-10-22  8:05     ` Ryo Tsuruta
2008-10-22  8:12       ` Chen Zumeng
2008-10-23 10:02       ` haotian
2008-10-23 11:28         ` Ryo Tsuruta
2008-10-22 10:38   ` Ryo Tsuruta

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=48FDB8AC.9020707@windriver.com \
    --to=zumeng.chen@windriver.com \
    --cc=agk@redhat.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=fernando@oss.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryov@valinux.co.jp \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.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