From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Chris J Arges <chris.j.arges@canonical.com>
Cc: hch@infradead.org, bruce.lucas@mongodb.com,
adam.radford@avagotech.com, kashyap.desai@avagotech.com,
Nagalakshmi Nandigama <nagalakshmi.nandigama@avagotech.com>,
Praveen Krishnamoorthy <praveen.krishnamoorthy@avagotech.com>,
Sreekanth Reddy <sreekanth.reddy@avagotech.com>,
Abhijit Mahajan <abhijit.mahajan@avagotech.com>,
MPT-FusionLinux.pdl@avagotech.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mptfusion: enable no_write_same for vmware scsi disks
Date: Tue, 23 Sep 2014 19:28:04 -0400 [thread overview]
Message-ID: <yq14mvxudbv.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <5421F020.1030309@canonical.com> (Chris J. Arges's message of "Tue, 23 Sep 2014 17:11:44 -0500")
>>>>> "Chris" == Chris J Arges <chris.j.arges@canonical.com> writes:
Chris> 1) Does this workaround make sense? Perhaps there is an easier
Chris> way?
One option is to ship a udev rule that disables write same on VMware
disks. However, I don't have a fundamental problem having a workaround
for this in the kernel.
Chris> 2) Do we expect changing max_write_same_blocks at the scsi_disk
Chris> level to propagate the right write_same flags to other layers
Chris> such as dm?
No, there's currently no way to communicate that the underlying topology
has changed.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-09-23 23:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 17:56 [PATCH] mptfusion: enable no_write_same in scsi_host_template Chris J Arges
2014-09-22 18:02 ` Christoph Hellwig
2014-09-22 18:17 ` Chris J Arges
2014-09-22 18:19 ` Christoph Hellwig
2014-09-22 18:50 ` Chris J Arges
2014-09-22 20:44 ` [PATCH v2] mptfusion: enable no_write_same for vmware scsi disks Chris J Arges
2014-09-22 20:54 ` Chris J Arges
2014-09-23 7:11 ` Christoph Hellwig
2014-09-23 14:22 ` [PATCH v3] " Chris J Arges
2014-09-23 15:29 ` Chris J Arges
2014-09-23 22:11 ` Chris J Arges
2014-09-23 23:28 ` Martin K. Petersen [this message]
2014-09-24 8:18 ` Christoph Hellwig
2014-09-24 15:11 ` Martin K. Petersen
2014-09-25 17:01 ` Christoph Hellwig
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=yq14mvxudbv.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=MPT-FusionLinux.pdl@avagotech.com \
--cc=abhijit.mahajan@avagotech.com \
--cc=adam.radford@avagotech.com \
--cc=bruce.lucas@mongodb.com \
--cc=chris.j.arges@canonical.com \
--cc=hch@infradead.org \
--cc=kashyap.desai@avagotech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nagalakshmi.nandigama@avagotech.com \
--cc=praveen.krishnamoorthy@avagotech.com \
--cc=sreekanth.reddy@avagotech.com \
/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.