From: Thomas Glanzmann <thomas@glanzmann.de>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: "Nicholas A. Bellinger" <nab@daterainc.com>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 0/3] target: Fixes for COMPARE_AND_WRITE backend I/O failure cases
Date: Thu, 3 Oct 2013 13:38:59 +0200 [thread overview]
Message-ID: <20131003113859.GB541@glanzmann.de> (raw)
In-Reply-To: <1380691034.19256.36.camel@haakon3.risingtidesystems.com>
Hallo Nab,
> Please let me know if you encounter any issues, and a patch to address
> this bit should be along in the next 24-48 hours.
I just did a little bit of stress testing:
- Rescan from 12 Initiators at the same time - PASS
- Deployed 24 VMs over 12 Initiators at the same time 200 MB/s
frontend traffic - PASS
- Booted 24 VMs on 12 ESX servers at the same time - 120 MB/s
frontend traffic - PASS
- Did 24 svMotion at the same time - 400 MB/s backend traffic -
10 MB/s frontend traffic using XCOPY. - PASS
- Unloaded the target in production, ran 'grep se_tmr
/proc/slabinfo' and loaded it again. And made sure that the
VMs continued to run. - PASS
It looks pretty stable to me. I'll use it next week in a class and
report back if I had any issues whatsoever. This was with:
v3.12-rc3-4-g8a77fe9
Cheers,
Thomas
next prev parent reply other threads:[~2013-10-03 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 0:13 [PATCH 0/3] target: Fixes for COMPARE_AND_WRITE backend I/O failure cases Nicholas A. Bellinger
2013-10-02 0:13 ` [PATCH 1/3] target: Reset data_length for COMPARE_AND_WRITE to NoLB * block_size Nicholas A. Bellinger
2013-10-02 0:13 ` [PATCH 2/3] target: Fix recursive COMPARE_AND_WRITE callback failure Nicholas A. Bellinger
2013-10-02 0:13 ` [PATCH 3/3] target: Fail on non zero scsi_status in compare_and_write_callback Nicholas A. Bellinger
2013-10-02 4:31 ` [PATCH 0/3] target: Fixes for COMPARE_AND_WRITE backend I/O failure cases Thomas Glanzmann
2013-10-02 5:17 ` Nicholas A. Bellinger
2013-10-03 11:38 ` Thomas Glanzmann [this message]
2013-10-03 12:14 ` Nicholas A. Bellinger
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=20131003113859.GB541@glanzmann.de \
--to=thomas@glanzmann.de \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@daterainc.com \
--cc=nab@linux-iscsi.org \
--cc=target-devel@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