All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kazuo Ito <ito.kazuo@oss.ntt.co.jp>
To: 7eggert@gmx.de
Cc: dm-devel@redhat.com, kjamieson@bycast.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dm-snapshot: poor copy-on-write performance due to I/O reordering
Date: Thu, 18 Sep 2008 10:10:28 +0900	[thread overview]
Message-ID: <48D1AA84.3050603@oss.ntt.co.jp> (raw)
In-Reply-To: <E1KfzFv-00041e-8A@be1.7eggert.dyndns.org>

Hi,

Bodo Eggert wrote:
> Kazuo Ito <ito.kazuo@oss.ntt.co.jp> wrote:
> 
>> Write throughput to LVM snapshot origin volume is an order
>> of magnitude slower than those to LV without snapshots or
>> snapshot target volumes, especially in the case of sequential
>> writes with O_SYNC on.
>>
>> The following patch originally written by Kevin Jamieson and
>> Jan Blunck and slightly modified for the current RCs by myself
>> tries to improve the performance by modifying the behaviour
>> of kcopyd, so that it pushes back an I/O job to the head of
>> the job queue instead of the tail as process_jobs() currently
>> does when it has to wait for free pages. This way, write
>> requests aren't shuffled to cause extra seeks.
> 
> Did you check for starvation problems, too?

I ran sadc along with the tests and figures like
%memused, kbbuffers and kbcached didn't change much
before and after the patch.  And since the buffered I/O
results didn't deteriorate at least in the cases of
10 and 100 megabyte sequential writes, I assumed
there should be plentiful of memory for the kernel
to use at least in these cases.

Anyway I can send you more detailed info upon your request.

Regards,

Kazuo Ito, NTT Open Source Software Center
Phone: +81-3-5860-5125 / FAX: +81-3-5463-5690 / E-mail: ito.kazuo@oss.ntt.co.jp

WARNING: multiple messages have this Message-ID (diff)
From: Kazuo Ito <ito.kazuo@oss.ntt.co.jp>
To: 7eggert@gmx.de
Cc: dm-devel@redhat.com, jblunck@suse.de, kjamieson@bycast.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dm-snapshot: poor copy-on-write performance due to I/O reordering
Date: Thu, 18 Sep 2008 10:10:28 +0900	[thread overview]
Message-ID: <48D1AA84.3050603@oss.ntt.co.jp> (raw)
In-Reply-To: <E1KfzFv-00041e-8A@be1.7eggert.dyndns.org>

Hi,

Bodo Eggert wrote:
> Kazuo Ito <ito.kazuo@oss.ntt.co.jp> wrote:
> 
>> Write throughput to LVM snapshot origin volume is an order
>> of magnitude slower than those to LV without snapshots or
>> snapshot target volumes, especially in the case of sequential
>> writes with O_SYNC on.
>>
>> The following patch originally written by Kevin Jamieson and
>> Jan Blunck and slightly modified for the current RCs by myself
>> tries to improve the performance by modifying the behaviour
>> of kcopyd, so that it pushes back an I/O job to the head of
>> the job queue instead of the tail as process_jobs() currently
>> does when it has to wait for free pages. This way, write
>> requests aren't shuffled to cause extra seeks.
> 
> Did you check for starvation problems, too?

I ran sadc along with the tests and figures like
%memused, kbbuffers and kbcached didn't change much
before and after the patch.  And since the buffered I/O
results didn't deteriorate at least in the cases of
10 and 100 megabyte sequential writes, I assumed
there should be plentiful of memory for the kernel
to use at least in these cases.

Anyway I can send you more detailed info upon your request.

Regards,

Kazuo Ito, NTT Open Source Software Center
Phone: +81-3-5860-5125 / FAX: +81-3-5463-5690 / E-mail: ito.kazuo@oss.ntt.co.jp

  reply	other threads:[~2008-09-18  1:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bd0gX-4ma-13@gated-at.bofh.it>
2008-09-17 15:47 ` [PATCH] dm-snapshot: poor copy-on-write performance due to I/O reordering Bodo Eggert
2008-09-18  1:10   ` Kazuo Ito [this message]
2008-09-18  1:10     ` Kazuo Ito
2008-09-24  5:55     ` [dm-devel] " Kazuo Ito
2008-09-17  8:03 Kazuo Ito
2008-09-17  8:03 ` Kazuo Ito

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=48D1AA84.3050603@oss.ntt.co.jp \
    --to=ito.kazuo@oss.ntt.co.jp \
    --cc=7eggert@gmx.de \
    --cc=dm-devel@redhat.com \
    --cc=kjamieson@bycast.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.