From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 16 09:37:14 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94C1EC6A for ; Tue, 16 Sep 2014 09:37:14 +0000 (UTC) Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C98CE6E for ; Tue, 16 Sep 2014 09:37:14 +0000 (UTC) Received: by mail-pd0-f174.google.com with SMTP id v10so8187277pde.19 for ; Tue, 16 Sep 2014 02:37:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=LQjOWmPDc/fpD2a1L6HIKkh6AtA5NCsSyAm1wZ7bO0M=; b=MWBFf63j4CQlv58iox2iMa7MygP9t9j413bCIQ43gWbrVoEp2uA6l4NPZsBoIjhC3w I/xDtNkYo1ry9OqmLak4YVAUYmSki1FMFPaIp3pzEE8q1dGeQkYo19y0cs2Gmk/SojOV fAZzZM7yFywC47f1J/AGFjw6aIn22XQ4GrNAApJewIshMW34+4LEAT8CrqnhBmxQmT9x cYkdMlDZ3txNCrX3GXSiEftkevtFgFRbzBGc34A9fizR4P55lORP7mrPgkgtKR1EF765 0yAB+VxUPeHt8NnuwXWxD9AGqMc1FgwkJFa5px4DCJHHH388TZkzQc6QhzBZ9BQPMnSw VR1Q== X-Received: by 10.67.1.9 with SMTP id bc9mr12531712pad.42.1410860234009; Tue, 16 Sep 2014 02:37:14 -0700 (PDT) Received: from Peters-MacAir.local ([106.39.255.231]) by mx.google.com with ESMTPSA id e11sm13633323pdm.47.2014.09.16.02.37.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 16 Sep 2014 02:37:12 -0700 (PDT) Message-ID: <541804B0.7070407@gmail.com> Date: Tue, 16 Sep 2014 17:36:48 +0800 From: Xu Zhe User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: How to disable hard disk write cache? Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 09:37:14 -0000 Hi, all, Does anyone knows how to disable write cache of hard disk? I have found some hints here at Freebsd website: https://www.freebsd.org/doc/handbook/configtuning-disk.html However, this seems only work for ATA devices, what about SAS/NLSAS devices (Meanwhile, it seems that there is no such sysctl in latest Freebsd release, which is 10.0)? Any hints are welcomed! Thanks in advance. Peter From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 16 12:46:31 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5126F14C for ; Tue, 16 Sep 2014 12:46:31 +0000 (UTC) Received: from cavuit01.kulnet.kuleuven.be (rhcavuit01.kulnet.kuleuven.be [IPv6:2a02:2c40:0:c0::25:129]) by mx1.freebsd.org (Postfix) with ESMTP id 0E455905 for ; Tue, 16 Sep 2014 12:46:30 +0000 (UTC) X-KULeuven-Envelope-From: bram.vandoren@ster.kuleuven.be X-Spam-Status: not spam, SpamAssassin (not cached, score=-51, required 5, autolearn=disabled, ALL_TRUSTED -1.00, LOCAL_SMTPS -50.00) X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: DF0DE20008.A0529 X-KULeuven-Information: Katholieke Universiteit Leuven Received: from icts-p-smtps-1.cc.kuleuven.be (icts-p-smtps-1e.kulnet.kuleuven.be [134.58.240.33]) by cavuit01.kulnet.kuleuven.be (Postfix) with ESMTP id DF0DE20008 for ; Tue, 16 Sep 2014 14:46:21 +0200 (CEST) Received: from miaplacidus.ster.kuleuven.be (unknown [10.33.178.95]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by icts-p-smtps-1.cc.kuleuven.be (Postfix) with ESMTPSA id DFAA14098 for ; Tue, 16 Sep 2014 14:46:18 +0200 (CEST) Message-ID: <5418311A.3080007@ster.kuleuven.be> Date: Tue, 16 Sep 2014 14:46:18 +0200 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Bram Vandoren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Re: How to disable hard disk write cache? References: <541804B0.7070407@gmail.com> In-Reply-To: <541804B0.7070407@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 12:46:31 -0000 On 09/16/2014 11:36 AM, Xu Zhe wrote: > Does anyone knows how to disable write cache of hard disk? Have a look at camcontrol modepage and the WCE bit. Cheers, Bram. From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 16 13:50:35 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C2590B72 for ; Tue, 16 Sep 2014 13:50:35 +0000 (UTC) Received: from smtp.infotech.no (smtp.infotech.no [82.134.31.41]) by mx1.freebsd.org (Postfix) with ESMTP id 7F6C2F9F for ; Tue, 16 Sep 2014 13:50:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.infotech.no (Postfix) with ESMTP id 3C5252041D4; Tue, 16 Sep 2014 15:50:27 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.6 (20110518) (Debian) at infotech.no Received: from smtp.infotech.no ([127.0.0.1]) by localhost (smtp.infotech.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ljjEVeyjE+U; Tue, 16 Sep 2014 15:50:25 +0200 (CEST) Received: from [192.168.48.86] (unknown [206.126.91.104]) by smtp.infotech.no (Postfix) with ESMTPA id A4C1C2041CE; Tue, 16 Sep 2014 15:50:24 +0200 (CEST) Message-ID: <54184016.7060208@interlog.com> Date: Tue, 16 Sep 2014 09:50:14 -0400 From: Douglas Gilbert Reply-To: dgilbert@interlog.com User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Bram Vandoren , freebsd-scsi@freebsd.org Subject: Re: How to disable hard disk write cache? References: <541804B0.7070407@gmail.com> <5418311A.3080007@ster.kuleuven.be> In-Reply-To: <5418311A.3080007@ster.kuleuven.be> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 13:50:35 -0000 On 14-09-16 08:46 AM, Bram Vandoren wrote: > On 09/16/2014 11:36 AM, Xu Zhe wrote: > >> Does anyone knows how to disable write cache of hard disk? > > Have a look at camcontrol modepage and the WCE bit. You could also use the sdparm utility: sdparm -c WCE From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 16 14:09:10 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7975E496 for ; Tue, 16 Sep 2014 14:09:10 +0000 (UTC) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anubis.delphij.net", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BF9827C for ; Tue, 16 Sep 2014 14:09:10 +0000 (UTC) Received: from delphij-macbook.local (unknown [1.202.68.57]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by anubis.delphij.net (Postfix) with ESMTPSA id 6DC6D1571A; Tue, 16 Sep 2014 07:09:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphij.net; s=anubis; t=1410876550; x=1410890950; bh=nCnOE5kQyoqDo6HjsuKxFQCj2+yuBikw7zmP8Ym7FgE=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=SllfeERpeUIyJRlY2472OnGTk1rAMECnXhykqgmfF9Ql1+8dEYjdGqEUsEc6hJBgM NNEiUdun7O/yiiASQ5k3LK1GY7FfacpkIrFyAgb74jOJ7cQLHAJohIwrHmzLdkYGgu Gtib/lm6Xgq1Ipztrt2nepkPu/ry0BbU7+Men6kc= Message-ID: <54184484.1070304@delphij.net> Date: Tue, 16 Sep 2014 22:09:08 +0800 From: Xin Li Reply-To: d@delphij.net Organization: The FreeBSD Project MIME-Version: 1.0 To: Xu Zhe , freebsd-scsi@freebsd.org Subject: Re: How to disable hard disk write cache? References: <541804B0.7070407@gmail.com> In-Reply-To: <541804B0.7070407@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 14:09:10 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 9/16/14 5:36 PM, Xu Zhe wrote: > Hi, all, > > Does anyone knows how to disable write cache of hard disk? > > I have found some hints here at Freebsd website: > > https://www.freebsd.org/doc/handbook/configtuning-disk.html > > However, this seems only work for ATA devices, what about SAS/NLSAS > devices (Meanwhile, it seems that there is no such sysctl in latest > Freebsd release, which is 10.0)? > > Any hints are welcomed! Why do you want to disable write cache in the first place? It's not needed for most configurations nowadays. Modern SATA/SAS/SCSI devices usually comes with the capability of tagged commands, allowing the OS to know when a write buffer is on stable storage. With this, file systems can easily implement the right semantics and recover from e.g. a power outage, etc. Cheers, -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJUGESDAAoJEJW2GBstM+ns2R4QAKKL2+TKfTaFQOWk4/jOKzdD 6yANm2ZYI3reChuUmbYjjchfce6nGcxz7EPjTOfBLj37p8bZFaW91e/ayviY9pNL QktP0hgTZp4EFLJSlPfqjx6f8aU2gJ640b/cKbIQkaxHWRLoHea8GJ2XhyVS9JfK o8aM+VPyxRrTRH0e2BQ8t0DMJohCrVNZ0fYSAKToDqI2RpcmOumYA4yChXb0hgvc Rz3PGZth19E4rxdNtOM0Ap/l4PL3+lInIlU8kPdwUaqvT11mxjUM+6zkF904VtqL 5xoURW/j9MAbFl6ozJJKnkfd20lCT3TfyQUC7weDOT8Jz78/8Sx2qy6ilkQCe0ZI AWV0hpoQPk2bzFxwB7wr9MiVbXJcpAHfHFcKTbLWY4NzY/8RknDt5dNsqsntlDww dSb1xRLdPQFBh7NrZA1GAfxXdfK8GNBONF+cRKutvFAlIzq0kywaa5baN1ZwLdU2 Kz3LJ0SLQMNEFioES+9j94fSeiW9LY9OJlI9EAjf2gys4WFeLkTgOgdBhvY935Mi j6FHk4xZmgKOS2s0c7UOYMjj6OgU1or4t2awMF/ObQwd8cmCT5abeGUdtrDGdCZu am/9nbCfR6FHhm5k90t+yCzl/hPf7dqVoz41bnP6+dD5q5zwxOhOc/SEiCJKCH3L iQoPiJfxH7JGZdCw/Vz+ =QSHo -----END PGP SIGNATURE----- From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 16 22:00:32 2014 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1E5FAF3E for ; Tue, 16 Sep 2014 22:00:32 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 05D291D1 for ; Tue, 16 Sep 2014 22:00:32 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GM0VKC046379 for ; Tue, 16 Sep 2014 22:00:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 193696] CAM AC_FOUND_DEVICE calls malloc(M_WAITOK) from THREAD_NO_SLEEPING() context Date: Tue, 16 Sep 2014 22:00:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 22:00:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193696 Garrett Cooper changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mav@FreeBSD.org Assignee|freebsd-bugs@FreeBSD.org |freebsd-scsi@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 17 03:04:49 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 060A6A12 for ; Wed, 17 Sep 2014 03:04:49 +0000 (UTC) Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CF78A5E8 for ; Wed, 17 Sep 2014 03:04:48 +0000 (UTC) Received: by mail-pd0-f178.google.com with SMTP id p10so1115233pdj.37 for ; Tue, 16 Sep 2014 20:04:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=WcBBFALocmkx2nPBp+UFhkKiXT9rfPTuFB1trJZttG8=; b=EGXPnLLY1JoNGlkfElL2/UdAe50g9H/0kM4vlDGjyeJIhX14rkmUnZzLdW8Abd/Qb1 LkLEyNXuN67YnHczcSmT31Vdlo9Mat2er3gis55N7exfHkTUHPGPrMMduAu05YTjGpH6 uAYYgV01hwNyWOuA8FaVn2R0dHmrbMJto4oPqdzsMQjfI9gFg40SanDU2iLZQD4OPnso qHKiLO9cn9L9ESCE2fhoBvDvKVf5mpY0xT7FATjNAuwX4oCBcBE9NN6JfyYBSCxaN7m5 V9alllGIm92Gm5WeszoBoHW9M8IVKY8X9gXi8YnebPUY7P65TEZmxycI/pbrkYIcgGw0 gdnQ== X-Received: by 10.70.64.166 with SMTP id p6mr636443pds.139.1410923088397; Tue, 16 Sep 2014 20:04:48 -0700 (PDT) Received: from Peters-MacAir.local ([106.39.255.231]) by mx.google.com with ESMTPSA id xt10sm15863848pab.44.2014.09.16.20.04.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 16 Sep 2014 20:04:48 -0700 (PDT) Message-ID: <5418FA4A.1050707@gmail.com> Date: Wed, 17 Sep 2014 11:04:42 +0800 From: Xu Zhe User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: d@delphij.net, freebsd-scsi@freebsd.org Subject: Re: How to disable hard disk write cache? References: <541804B0.7070407@gmail.com> <54184484.1070304@delphij.net> In-Reply-To: <54184484.1070304@delphij.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 03:04:49 -0000 于 14-9-16 22:09, Xin Li 写道: > On 9/16/14 5:36 PM, Xu Zhe wrote: >> > Hi, all, >> > >> > Does anyone knows how to disable write cache of hard disk? >> > >> > I have found some hints here at Freebsd website: >> > >> > https://www.freebsd.org/doc/handbook/configtuning-disk.html >> > >> > However, this seems only work for ATA devices, what about SAS/NLSAS >> > devices (Meanwhile, it seems that there is no such sysctl in latest >> > Freebsd release, which is 10.0)? >> > >> > Any hints are welcomed! > Why do you want to disable write cache in the first place? It's not > needed for most configurations nowadays. > > Modern SATA/SAS/SCSI devices usually comes with the capability of > tagged commands, allowing the OS to know when a write buffer is on > stable storage. With this, file systems can easily implement the > right semantics and recover from e.g. a power outage, etc. > > Cheers, Hi, Xin, Thanks for the reply. My final goal is not to disable write cache. I just want to do a simple test to see how would the IOPS drop when write cache disabled (I suppose without disk write cache, the value should be the same as IOPS of random read, both using O_DIRECT flag to avoid system cache, etc.). Meanwhile, what I really want to know is that, how could I make sure IO is persistent as long as I got reply from hard disk? Since I suppose all file systems require this assumption to achieve self consistency. I have googled about the "tagged command" but only found something related to TCQ, which mainly talks about the queueing but not anything related to cache sync. Any more hints? I saw some pages that mentioned about SATA FUA command support on Linux (Which I guess is what I am looking for): https://www.kernel.org/doc/Documentation/block/writeback_cache_control.txt However, I have not found useful information related to Freebsd. :( Peter From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 17 06:49:05 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB23E5BC for ; Wed, 17 Sep 2014 06:49:05 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 55A44E89 for ; Wed, 17 Sep 2014 06:49:05 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id em10so4928542wid.1 for ; Tue, 16 Sep 2014 23:49:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LxnAB+NZd8hEMHMRLw3uggW4UdoxoBnyobh2V3pxCrI=; b=i4E8sSgqkYvst3Bj5TqtUTaACynYTisPiKr16ORZ+NhnLYAMr2ISpGx38R1B9ZGSOn i8njyUSVColi7+wx+2/8Hm9iQwpMvguQwU+BBAFuIYcGx1mfZYvnjD9wvo0xyKtR4kYS lGuP+9WijvRSnqNVVhG37CrZLP50z9R//EV767rgilCE7W58m4/VjzZxhtJ/FIqxuyHz abOnFJyP05BWtYjrCx2ocxqpn1pbWxREXCk/6XfqYIqbRkUAiFgI9/l741wR8yqgComF esiniJ5ZMYUaAMjA8/Xim+BlMOANHw47KMRloPGYpyhGUaofXOFIkFZUYsZdwbTjC6Go mjDQ== MIME-Version: 1.0 X-Received: by 10.180.38.114 with SMTP id f18mr3461221wik.24.1410936543353; Tue, 16 Sep 2014 23:49:03 -0700 (PDT) Received: by 10.216.6.129 with HTTP; Tue, 16 Sep 2014 23:49:03 -0700 (PDT) In-Reply-To: <14D38CFE3887426D9065E26F50457F30@multiplay.co.uk> References: <93D764A8-01AE-42FA-8020-65CEB6C7D64C@sarenet.es> <14D38CFE3887426D9065E26F50457F30@multiplay.co.uk> Date: Tue, 16 Sep 2014 23:49:03 -0700 Message-ID: Subject: Re: Samsung 840 Pro SSD and quirks From: Jason Wolfe To: Steven Hartland Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD-scsi X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 06:49:05 -0000 We run the Samsung 843T drives, which are basically 840s with extra flash for over provisioning. We have directly from Samsung that they are in fact 4k drives, which led to the quirk addition for the 843T in r270305. Anyway, just wanted to round the thread out with some confirmation. Jason On Tue, Sep 2, 2014 at 8:07 AM, Steven Hartland wrote: > Thanks for the confirmation Borja I was a little confused why > our two results differed. > > For a 12 disk system you'll likely need two SAS2 controllers, > or at least 12 SAS lines otherwise you will hit controller > throughput issues as a 840 can pretty much saturate a single > SAS2 lane on its own. > > At that point you'll also start to see other issues. > > I'd strongly suggest moving to stable/10, if you haven't already, > particularly if you have large amount of RAM in the system > otherwise you will become CPU bound on ARC hash lookups. > > Regards > Steve > > ----- Original Message ----- From: "Borja Marcos" > To: "Steven Hartland" > Cc: "FreeBSD-scsi" > Sent: Tuesday, September 02, 2014 3:48 PM > Subject: Re: Samsung 840 Pro SSD and quirks > > > > > On Sep 1, 2014, at 5:44 PM, Steven Hartland wrote: > > We saw a noticable performance increase on 4k on our 8TB 840 >> array but I too couldn't find any concrete information either. >> >> If anyone has this info and can confirm either way that would >> be great. >> > > I stand corrected. I have done some benchmarks with just two Samsung SSDs > (zpool with two disks, no mirroring) and indeed I get better performance > with 4 KB blocks. > > I did my original tests with 12 disks and some other bottleneck was hiding > the performance difference. > > In both cases, anyway, Trim was working unless the system lies. > > > > > > Thanks! > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 17 06:52:05 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7CA3261B for ; Wed, 17 Sep 2014 06:52:05 +0000 (UTC) Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com [195.16.151.151]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 34DD2F27 for ; Wed, 17 Sep 2014 06:52:04 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop04.sare.net (Postfix) with ESMTPSA id 19EA99DC7FF; Wed, 17 Sep 2014 08:51:56 +0200 (CEST) Subject: Re: Samsung 840 Pro SSD and quirks Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: Date: Wed, 17 Sep 2014 08:51:51 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <93D764A8-01AE-42FA-8020-65CEB6C7D64C@sarenet.es> <14D38CFE3887426D9065E26F50457F30@multiplay.co.uk> To: Jason Wolfe X-Mailer: Apple Mail (2.1283) Cc: FreeBSD-scsi X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 06:52:05 -0000 On Sep 17, 2014, at 8:49 AM, Jason Wolfe wrote: > We run the Samsung 843T drives, which are basically 840s with extra = flash for over provisioning. We have directly from Samsung that they = are in fact 4k drives, which led to the quirk addition for the 843T in = r270305. Anyway, just wanted to round the thread out with some = confirmation. Thank you. Some official word always helps! Borja. From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 17:05:55 2014 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E7DC2CB7 for ; Fri, 19 Sep 2014 17:05:55 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CEAAEE82 for ; Fri, 19 Sep 2014 17:05:55 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8JH5tbP053018 for ; Fri, 19 Sep 2014 17:05:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 193696] CAM AC_FOUND_DEVICE calls malloc(M_WAITOK) from THREAD_NO_SLEEPING() context Date: Fri, 19 Sep 2014 17:05:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bdrewery@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2014 17:05:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193696 --- Comment #4 from Bryan Drewery --- Kib had some feedback on the assert: 1. We should also add it (and the interrupt check) to uma_zalloc_arg() (through 1 inline function) 2. The interrupt assert may be wrong since it is not OK to malloc(9) in an interrupt, regardless of the flags. Isilon's internal discussion was that we should add a debug stack output rather than an assert until all major cases are fixed. -- You are receiving this mail because: You are the assignee for the bug.