From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Martin K. Petersen" Subject: Re: [PATCH v3] mptfusion: enable no_write_same for vmware scsi disks Date: Tue, 23 Sep 2014 19:28:04 -0400 Message-ID: References: <20140923071154.GB3867@infradead.org> <1411482160-32007-1-git-send-email-chris.j.arges@canonical.com> <5421F020.1030309@canonical.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <5421F020.1030309@canonical.com> (Chris J. Arges's message of "Tue, 23 Sep 2014 17:11:44 -0500") Sender: linux-kernel-owner@vger.kernel.org To: Chris J Arges Cc: hch@infradead.org, bruce.lucas@mongodb.com, adam.radford@avagotech.com, kashyap.desai@avagotech.com, Nagalakshmi Nandigama , Praveen Krishnamoorthy , Sreekanth Reddy , Abhijit Mahajan , MPT-FusionLinux.pdl@avagotech.com, linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-scsi@vger.kernel.org >>>>> "Chris" == Chris J Arges 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