public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 12752] megaraid-sas driver performance worse than on-board sata_nv
Date: Fri, 10 Jun 2011 23:05:04 GMT	[thread overview]
Message-ID: <201106102305.p5AN54hl028552@demeter2.kernel.org> (raw)
In-Reply-To: <bug-12752-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=12752


Adam Radford <aradford@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aradford@gmail.com




--- Comment #2 from Adam Radford <aradford@gmail.com>  2011-06-10 23:05:02 ---
devsk,

I'm sorry about you not getting a response from the previous megaraid_sas
developer.  He was probably not watching bugzilla.kernel.org.

There is nothing in the driver that will 'throttle' the I/O on your PERC5
controller.

The software raid code sets various read-ahead values in the block layer
request_queues it sets up:

# grep -i "ra_pages" *
raid0.c:         * If an individual device has an ra_pages greater than the
raid0.c:                if (mddev->queue->backing_dev_info.ra_pages < 2*
stripe)
raid0.c:                        mddev->queue->backing_dev_info.ra_pages = 2*
stripe;
raid10.c:               if (mddev->queue->backing_dev_info.ra_pages < 2*
stripe)
raid10.c:                       mddev->queue->backing_dev_info.ra_pages = 2*
stripe;
raid5.c:                if (mddev->queue->backing_dev_info.ra_pages < 2 *
stripe)
raid5.c:                        mddev->queue->backing_dev_info.ra_pages = 2 *
stripe;
raid5.c:                        if
(conf->mddev->queue->backing_dev_info.ra_pages < 2 * stripe)
raid5.c:                               
conf->mddev->queue->backing_dev_info.ra_pages = 2 * stripe;

Can you try setting some OS read-ahead values (on top of the controller doing
read-ahead) for the scsi device attached to your PERC5 controller and
re-running 
your tests?

i.e.:

/sbin/blockdev --getra /dev/sda (See what you have set currently)
/sbin/blockdev --setra 8192 /dev/sda (Set read ahead for sda to 8192 sectors)
/sbin/blockdev --setra 16834 /dev/sda (Set read ahead for sda to 16384 sectors)

This may cause more I/O to be issued to the card from the OS and may improve
your bonnie++ results.

-Adam

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2011-06-10 23:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12752-11613@https.bugzilla.kernel.org/>
2011-06-10  4:03 ` [Bug 12752] megaraid-sas driver performance worse than on-board sata_nv bugzilla-daemon
2011-06-10 23:05 ` bugzilla-daemon [this message]
2011-06-12 18:51 ` bugzilla-daemon
2012-05-30 14:13 ` bugzilla-daemon
2012-05-30 14:13 ` bugzilla-daemon

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=201106102305.p5AN54hl028552@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox