All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: scst-devel <scst-devel@lists.sourceforge.net>,
	Jens Axboe <jens.axboe@oracle.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Scst-devel] Linux kernel and block I/O performance
Date: Tue, 31 Mar 2009 21:39:32 +0400	[thread overview]
Message-ID: <49D25554.3020504@vlnb.net> (raw)
In-Reply-To: <e2e108260903251117n54d0275bk8bf7c9398d9987da@mail.gmail.com>

Hello

Bart Van Assche, on 03/25/2009 09:17 PM wrote:
> Hello,
> 
> For anyone who's running SCST performance measurements, please have a
> look at http://lwn.net/Articles/325307/. In this article it is
> explained why 2.6.25 and 2.6.29 perform three times faster on some I/O
> benchmarks than 2.6.26, 2.6.27 and 2.6.28. The relevant kernel commits
> are:
> 
> 2.6.26: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=18ce3751ccd488c78d3827e9f6bf54e6322676fb
> 2.6.29: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=78f707bfc723552e8309b7c38a8d0cc51012e813

Interesting. I've just checked with 2.6.29 on the target. With iSCSI 
still ext3 as a backstorage FS on the target a lot slower on writes than 
xfs (25-100%, deviation between runs is very high). On my system it's 
something like 50-80MB/s vs 100+MB/s. In both cases initiator formatted 
the device in ext3. Test application was famous "dd if=/dev/zero 
of=/mnt/q bs=512K".

Thanks,
Vlad

           reply	other threads:[~2009-03-31 17:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <e2e108260903251117n54d0275bk8bf7c9398d9987da@mail.gmail.com>]

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=49D25554.3020504@vlnb.net \
    --to=vst@vlnb.net \
    --cc=bart.vanassche@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scst-devel@lists.sourceforge.net \
    /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.