Changes in Makefile

d12e91d5 - Make dnode definition uniform on !x86

Tue, 21 Aug 2018 03:45:09 +0000

Make dnode definition uniform on !x86gcc4 requires -fms-extensions to accept anonymous union members List of files: /freebsd-12.1/sys/modules/zfs/Makefile

193d9e76 - sys/modules: normalize .CURDIR-relative paths to SRCTOP

Sat, 04 Mar 2017 10:10:17 +0000

sys/modules: normalize .CURDIR-relative paths to SRCTOPThis simplifies make output/logicTested with: `cd sys/modules; make ALL_MODULES=` on amd64MFC after: 1 monthSponsored by: Dell EMC Isilon List of files: /freebsd-12.1/sys/modules/zfs/Makefile

7fa27112 - zfs: clean up unused files and definitions

Fri, 24 Feb 2017 07:53:56 +0000

zfs: clean up unused files and definitionsMFC after: 1 monthX-MFC after: r314048 List of files: /freebsd-12.1/sys/modules/zfs/Makefile

d9dbd70b - Update CFLAGS for clang compatibility

Tue, 31 Jan 2017 01:55:29 +0000

Update CFLAGS for clang compatibility* Clang/llvm does not (yet) support -m(no-)spe, so make it gcc-only* Clang now supports -msoft-float, and does not appear to recognize "-disable-ppc-float-in-variadic", which appears to have been a crutch until soft-float was implemented. It's now implemented for both 32- and 64-bit.* Clang/llvm use a 'medium' code model by default for powerpc64, supporting up to 4GB TOC, and does not support the '-mminimal-toc' option. Given both of these, make -mminimal-toc gcc-only.MFC after: 2 weeks List of files: /freebsd-12.1/sys/modules/zfs/Makefile

0144ad3e - Connect the SHA-512t256 and Skein hashing algorithms to ZFS

Tue, 31 May 2016 04:12:14 +0000

Connect the SHA-512t256 and Skein hashing algorithms to ZFSSupport for the new hashing algorithms in ZFS was introduced in r289422However it was disconnected because FreeBSD lacked implementations ofSHA-512 (truncated to 256 bits), and Skein.These implementations were introduced in r300921 and r300966 respectivelyThis commit connects them to ZFS and enabled these new checksum algorithmsThis new algorithms are not supported by the boot blocks, so do not use themon your root dataset if you boot from ZFS.Relnotes: yesSponsored by: ScaleEngine Inc. List of files: /freebsd-12.1/sys/modules/zfs/Makefile

7a3f5d11 - Replace sys/crypto/sha2/sha2.c with lib/libmd/sha512c.c

Sun, 27 Dec 2015 17:33:59 +0000

Replace sys/crypto/sha2/sha2.c with lib/libmd/sha512c.ccperciva's libmd implementation is 5-30% fasterThe same was done for SHA256 previously in r263218cperciva's implementation was lacking SHA-384 which I implemented, validated against OpenSSL and the NIST documentationExtend sbin/md5 to create sha384(1)Chase dependancies on sys/crypto/sha2/sha2.{c,h} and replace them with sha512{c.c,.h}Reviewed by: cperciva, des, delphijApproved by: secteam, bapt (mentor)MFC after: 2 weeksSponsored by: ScaleEngine Inc.Differential Revision: https://reviews.freebsd.org/D3929 List of files: /freebsd-12.1/sys/modules/zfs/Makefile

e945651a - Revert r286984 (adding opt_random.h to sys/modules/zfs/Makefile)

Tue, 08 Sep 2015 08:54:40 +0000

Revert r286984 (adding opt_random.h to sys/modules/zfs/Makefile)opt_random.h is no longer needed/referenced in the kernel buildX-MFC with: r287558 List of files: /freebsd-12.1/sys/modules/zfs/Makefile

23d10468 - fix standalone build of zfs module

Fri, 21 Aug 2015 08:06:18 +0000

fix standalone build of zfs moduleNot sure if this is a proper fix, but it does the job. List of files: /freebsd-12.1/sys/modules/zfs/Makefile

79b7e3e2 - Fix `make depend` in sys/modules

Wed, 05 Aug 2015 14:45:52 +0000

Fix `make depend` in sys/modulesReviewed by: delphijDifferential Revision: https://reviews.freebsd.org/D3291 List of files: /freebsd-12.1/sys/modules/zfs/Makefile

306a82f8 - Rename zfs nvpair files to not colidate with our nvlist.

Thu, 09 Jul 2015 21:53:40 +0000

Rename zfs nvpair files to not colidate with our nvlist.PR: 201356Approved by: pjd (mentor) List of files: /freebsd-12.1/sys/modules/zfs/Makefile

4906cdc8 - Re-support CWARNFLAGS, lost when bsd.sys.mk was removed. Also, support

Sat, 03 Jan 2015 03:35:18 +0000

Re-support CWARNFLAGS, lost when bsd.sys.mk was removed. Also, supportCWARNFALGS.$file centrally so we don't have to have it in all theplaces. Remove a few warning flags that are no longer needed.Also, always use -Wno-unknown-pragma to (hopefully temporarily) workaround #pragma ident in debug.h in the opensolaris code. Remove somestale warning suppression that's no longer necessary. List of files: /freebsd-12.1/sys/modules/zfs/Makefile

afb13fc2 - Instead of requiring an edit to turn on ZFS debugging, define ZFS_DEBUG.

Wed, 01 Oct 2014 15:34:48 +0000

Instead of requiring an edit to turn on ZFS debugging, define ZFS_DEBUG.MFC after: 1 month List of files: /freebsd-12.1/sys/modules/zfs/Makefile

71f3caaf - Add dtrace probe support for zfs SET_ERROR(..)

Thu, 18 Sep 2014 20:00:36 +0000

Add dtrace probe support for zfs SET_ERROR(..)MFC after: 1 weekSponsored by: Multiplay List of files: /freebsd-12.1/sys/modules/zfs/Makefile

0327754b - Avoid using ${.CURDIR} so that the module can be built from multiple

Sat, 26 Jul 2014 17:24:58 +0000

Avoid using ${.CURDIR} so that the module can be built from multipledirectories.Obtained from: Juniper Networks, Inc. List of files: /freebsd-12.1/sys/modules/zfs/Makefile

f225bcd1 - I clearly didn't test the modules... add sha256c.c to the various

Sun, 16 Mar 2014 01:55:30 +0000

I clearly didn't test the modules... add sha256c.c to the variousmodules that included sha2.c... List of files: /freebsd-12.1/sys/modules/zfs/Makefile

c319ea15 - opensolaris code: translate INVARIANTS to DEBUG and ZFS_DEBUG

Tue, 06 Aug 2013 15:51:56 +0000

opensolaris code: translate INVARIANTS to DEBUG and ZFS_DEBUGDo this by forcing inclusion ofsys/cddl/compat/opensolaris/sys/debug_compat.hvia -include option into all source files from OpenSolaris.Note that this -include option must always be after -include opt_global.h.Additionally, remove forced definition of DEBUG for some modules and fixtheir build without DEBUG.Also, meaning of DEBUG was overloaded to enable WITNESS support for someOpenSolaris (primarily ZFS) locks. Now this overloading is removed andthat use of DEBUG is replaced with a new option OPENSOLARIS_WITNESS.MFC after: 17 days List of files: /freebsd-12.1/sys/modules/zfs/Makefile

89f6b863 - Switch the vm_object mutex to be a rwlock. This will enable in the

Sat, 09 Mar 2013 02:32:23 +0000

Switch the vm_object mutex to be a rwlock. This will enable in thefuture further optimizations where the vm_object lock will be heldin read mode most of the time the page cache resident pool of pagesare accessed for reading purposes.The change is mostly mechanical but few notes are reported:* The KPI changes as follow: - VM_OBJECT_LOCK() -> VM_OBJECT_WLOCK() - VM_OBJECT_TRYLOCK() -> VM_OBJECT_TRYWLOCK() - VM_OBJECT_UNLOCK() -> VM_OBJECT_WUNLOCK() - VM_OBJECT_LOCK_ASSERT(MA_OWNED) -> VM_OBJECT_ASSERT_WLOCKED() (in order to avoid visibility of implementation details) - The read-mode operations are added: VM_OBJECT_RLOCK(), VM_OBJECT_TRYRLOCK(), VM_OBJECT_RUNLOCK(), VM_OBJECT_ASSERT_RLOCKED(), VM_OBJECT_ASSERT_LOCKED()* The vm/vm_pager.h namespace pollution avoidance (forcing requiring sys/mutex.h in consumers directly to cater its inlining functions using VM_OBJECT_LOCK()) imposes that all the vm/vm_pager.h consumers now must include also sys/rwlock.h.* zfs requires a quite convoluted fix to include FreeBSD rwlocks into the compat layer because the name clash between FreeBSD and solaris versions must be avoided. At this purpose zfs redefines the vm_object locking functions directly, isolating the FreeBSD components in specific compat stubs.The KPI results heavilly broken by this commit. Thirdy part ports mustbe updated accordingly (I can think off-hand of VirtualBox, for example).Sponsored by: EMC / Isilon storage divisionReviewed by: jeffReviewed by: pjd (ZFS specific review)Discussed with: alcTested by: pho List of files: /freebsd-12.1/sys/modules/zfs/Makefile

bcb77be2 - Add TRIM support.

Sun, 23 Sep 2012 19:40:58 +0000

Add TRIM support.The code builds a map of regions that were freed. On every write thecode consults the map and eventually removes ranges that were freedbefore, but are now overwritten.Freed blocks are not TRIMed immediately. There is a tunable that defineshow many txg we should wait with TRIMming freed blocks (64 by default).There is a low priority thread that TRIMs ranges when the time comes.During TRIM we keep in-flight ranges on a list to detect collidingwrites - we have to delay writes that collide with in-flight TRIMs incase something will be reordered and write will reached the disk beforethe TRIM. We don't have to do the same for in-flight writes, ascolliding writes just remove ranges to TRIM.Sponsored by: multiplay.co.ukThis work includes some important fixes and some improvements obtainedfrom the zfsonlinux project, including TRIMming entire vdevs on poolcreate/add/attach and on pool import for spare and cache vdevs.Obtained from: zfsonlinuxSubmitted by: Etienne Dechamps List of files: /freebsd-12.1/sys/modules/zfs/Makefile

665b912a - MFC r207920,r207934,r207936,r207937,r207970,r208142,r208147,r208148,r208166,

Mon, 24 May 2010 10:09:36 +0000

MFC r207920,r207934,r207936,r207937,r207970,r208142,r208147,r208148,r208166,r208454,r208455,r208458:r207920:Back out r205134. It is not stable.r207934:Add missing new line characters to the warnings.r207936:Eventhough r203504 eliminates taste traffic provoked by vdev_geom.c,ZFS still like to open all vdevs, close them and open them again,which in turn provokes taste traffic anyway.I don't know of any clean way to fix it, so do it the hard way - if we can'topen provider for writing just retry 5 times with 0.5 pauses. This shouldelimitate accidental races caused by other classes tasting providers created ontop of our vdevs.Reported by: James R. Van Artsdalen Reported by: Yuri Pankov r207937:I added vfs_lowvnodes event, but it was only used for a short while and nowit is totally unused. Remove it.r207970:When there is no memory or KVA, try to help by reclaiming some vnodes.This helps with 'kmem_map too small' panics.No objections from: kibTested by: Alexander V. Ribchansky r208142:The whole point of having dedicated worker thread for each leaf VDEV was toavoid calling zio_interrupt() from geom_up thread context. It turns out thatwhen provider is forcibly removed from the system and we kill worker threadthere can still be some ZIOs pending. To complete pending ZIOs when there isno worker thread anymore we still have to call zio_interrupt() from geom_upcontext. To avoid this race just remove use of worker threads altogether.This should be more or less fine, because I also thought that zio_interrupt()does more work, but it only makes small UMA allocation with M_WAITOK.It also saves one context switch per I/O request.PR: kern/145339Reported by: Alex Bakhtin r208147:Add task structure to zio and use it instead of allocating one.This eliminates the only place where we can sleep when calling zio_interrupt().As a side-effect this can actually improve performance a little as weallocate one less thing for every I/O.Prodded by: kibr208148:Allow to configure UMA usage for ZIO data via loader and turn it on bydefault for amd64. On i386 I saw performance degradation when UMA was used,but for amd64 it should help.r208166:Fix userland build by making io_task available only for the kernel and byproviding taskq_dispatch_safe() macro.r208454:Remove ZIO_USE_UMA from arc.c as well.r208455:ZIO_USE_UMA is no longer used.r208458:Create UMA zones unconditionally. List of files: /freebsd-12.1/sys/modules/zfs/Makefile

3a482ccc - MFC r203504,r204067,r204073,r204101,r204804,r205079,r205080,r205132,r205133,

Sun, 18 Apr 2010 21:36:34 +0000

MFC r203504,r204067,r204073,r204101,r204804,r205079,r205080,r205132,r205133, r205134,r205231,r205253,r205264,r205346,r206051,r206667,r206792,r206793, r206794,r206795,r206796,r206797:r203504:Open provider for writting when we find the right one. Opening too muchproviders for writing provokes huge traffic related to taste events sendby GEOM on close. This can lead to various problems with opening GEOMproviders that are created on top of other GEOM providers.Reorted by: Kurt Touet , mrTested by: mr, Baginski Darren r204067:Update comment. We also look for GPT partitions.r204073:Add tunable and sysctl to skip hostid check on pool import.r204101:Don't set f_bsize to recordsize. It might confuse some software (like squid).Submitted by: Alexander Zagrebin r204804:Remove racy assertion.Reported by: Attila Nagy Obtained from: OpenSolaris, Bug ID 6827260r205079:Remove bogus assertion.Reported by: Johan Ström Obtained from: OpenSolaris, Bug ID 6920880r205080:Force commit to correct Bug ID:Obtained from: OpenSolaris, Bug ID 6920880r205132:Don't bottleneck on acquiring the stream locks - this avoids a massivedrop off in throughput with large numbers of simultaneous readsr205133:fix compilation under ZIO_USE_UMAr205134:make UMA the default allocator for ZFS buffers - this avoidsa great deal of contention in kmem_allocr205231:- reduce contention by breaking up ARC state locks in to 16 for data and 16 for metadata- export L2ARC tunables as sysctls- add several kstats to track L2ARC state more precisely- avoid holding a contended lock when atomically incrementing a contended counter (no lock protection needed for atomics)r205253:use CACHE_LINE_SIZE instead of hardcoding 128 for lock padpointed out by Marius Nuennerich and jhb@r205264:- cache line align arcs_lock array (h/t Marius Nuennerich)- fix ARCS_LOCK_PAD to use architecture defined CACHE_LINE_SIZE- cache line align buf_hash_table ht_locks arrayr205346:The same code is used to import and to create pool.The order of operations is the following:1. Try to open vdev by remembered path and guid.2. If 1 failed, try to find vdev which guid matches and ignore the path.3. If 2 failed this means either that the vdev we're looking for is gone or that pool is being created and vdev doesn't contain proper guid yet. To be able to handle pool creation we open vdev by path anyway.Because of 3 it is possible that we open wrong vdev on import which can lead toconfusions.The solution for this is to check spa_load_state. On pool creation it will beequal to SPA_LOAD_NONE and we can open vdev only by path immediately and if itis not equal to SPA_LOAD_NONE we first open by path+guid and when that fails,we open by guid. We no longer open wrong vdev on import.r206051:IOCPARM_MAX defines maximum size of a structure that can be passeddirectly to ioctl(2). Because of how ioctl command is build using _IO*()macros we have only 13 bits to encode structure size. So the structurecan be up to 8kB-1.Currently we define IOCPARM_MAX as PAGE_SIZE.This is IMHO wrong for three main reasons:1. It is confusing on archs with page size larger than 8kB (not really sure if we support such archs (sparc64?)), as even if PAGE_SIZE is bigger than 8kB, we won't be able to encode anything larger in ioctl command.2. It is a waste. Why the structure can be only 4kB on most archs if we have 13 bits dedicated for that, not 12?3. It shouldn't depend on architecture and page size. My ioctl command can work on one arch, but can't on the other?Increase IOCPARM_MAX to 8kB and make it independed of PAGE_SIZE andarchitecture it is compiled for. This allows to use all the bits on all thearchs for size. Note that this doesn't mean we will copy more on every ioctl(2)call. No. We still copyin(9)/copyout(9) only exact number of bytes encoded inioctl command.Practical use for this change is ZFS. zfs_cmd_t structure used for ZFSioctls is larger than 4kB.Silence on: arch@r206667:Fix 3-way deadlock that can happen because of ZFS and vnode lockorder reversal.thread0 (vfs_fhtovp) thread1 (vop_getattr) thread2 (zfs_recv)-------------------- --------------------- ------------------ vn_lockrrw_enter_read rrw_enter_write (hangs) rrw_enter_read (hangs)vn_lock (hangs)Reported by: Attila Nagy r206792:Set ARC_L2_WRITING on L2ARC header creation.Obtained from: OpenSolarisr206793:Remove racy assertion.Obtained from: OpenSolarisr206794:Extend locks scope to match OpenSolaris.r206795:Add missing list and lock destruction.r206796:Style fixes.r206797:Restore previous order. List of files: /freebsd-12.1/sys/modules/zfs/Makefile