From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 41552] Performance of writing and reading from multiple drives decreases by 40% when going from Linux Kernel 2.6.36.4 to 2.6.37 (and beyond)
Date: Tue, 23 Aug 2011 14:38:55 GMT [thread overview]
Message-ID: <201108231438.p7NEctlj014043@demeter1.kernel.org> (raw)
In-Reply-To: <bug-41552-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=41552
--- Comment #10 from Anonymous Emailer <anonymous@kernel-bugs.osdl.org> 2011-08-23 14:38:52 ---
Reply-To: James.Bottomley@HansenPartnership.com
On Mon, 2011-08-22 at 21:07 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> We were using the default CFQ scheduler. I will change it to deadline and see
> what happens. Also, we are not using a file system to perform the writes,
> rather we are sending SCSI commands directly to the devices, nor are we doing
> anything special to the disks with a device mapper. We simply write to each
> one on a different thread one sector at a time.
>
> I will attempt to get the trace and will add it if I can.
If you're just using a SG_IO type scsi command, then virtually nothing
we've done in block/scsi should affect this; certainly not the elevators
since we don't do merging on SG_IO, we just use them for queueing.
Since you say "write to each one on a different thread", it's possible
that some scheduler change may have impacted this.
James
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-08-23 14:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 15:20 [Bug 41552] New: Performance of writing and reading from multiple drives decreases by 40% when going from Linux Kernel 2.6.36.4 to 2.6.37 (and beyond) bugzilla-daemon
2011-08-22 15:21 ` [Bug 41552] " bugzilla-daemon
2011-08-22 15:22 ` bugzilla-daemon
2011-08-22 15:22 ` bugzilla-daemon
2011-08-22 19:25 ` bugzilla-daemon
2011-08-22 19:25 ` bugzilla-daemon
2011-08-22 20:21 ` bugzilla-daemon
2011-08-22 20:21 ` bugzilla-daemon
2011-08-22 20:24 ` bugzilla-daemon
2011-08-22 21:02 ` bugzilla-daemon
2011-08-22 21:07 ` bugzilla-daemon
2011-08-23 14:00 ` James Bottomley
2011-08-23 14:38 ` bugzilla-daemon [this message]
2011-08-24 20:46 ` bugzilla-daemon
2011-08-25 21:02 ` bugzilla-daemon
2012-08-30 10:41 ` 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=201108231438.p7NEctlj014043@demeter1.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 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.