From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 42939] hv_storvsc - write cache enabled by default and cannot be disabled
Date: Mon, 19 Mar 2012 19:36:47 GMT [thread overview]
Message-ID: <201203191936.q2JJal3M027532@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42939-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42939
--- Comment #2 from Mark <bugzilla-kernel-org-sux2k0@mstier.de> 2012-03-19 19:36:47 ---
Additional information (5):
I'm getting 1.000 subsequent (serialized and small -- integer inserts)
transactions done (locally) within 2.2 seconds -- with InnoDB ACID transactions
(ie. full data transaction sync enabled). Isn't that a bit too fast for cheap
SATA disks in a RAID10 config?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
prev parent reply other threads:[~2012-03-19 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 21:56 [Bug 42939] New: hv_storvsc - write cache enabled by default and cannot be disabled bugzilla-daemon
2012-03-15 21:57 ` [Bug 42939] " bugzilla-daemon
2012-03-19 19:33 ` bugzilla-daemon
2012-03-19 19:36 ` bugzilla-daemon [this message]
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=201203191936.q2JJal3M027532@bugzilla.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