2010-08-26 18:22:58 +00:00
|
|
|
MODULE := zfs
|
|
|
|
|
2012-07-09 09:23:00 +00:00
|
|
|
EXTRA_CFLAGS = $(ZFS_MODULE_CFLAGS) @KERNELCPPFLAGS@
|
2010-08-26 18:22:58 +00:00
|
|
|
|
2012-07-09 09:23:00 +00:00
|
|
|
obj-$(CONFIG_ZFS) := $(MODULE).o
|
2010-08-26 18:22:58 +00:00
|
|
|
|
2010-09-04 20:26:23 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/arc.o
|
2014-06-05 21:19:08 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/blkptr.o
|
2010-09-04 20:26:23 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/bplist.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/bpobj.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dbuf.o
|
2013-10-03 00:11:19 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dbuf_stats.o
|
2012-12-13 23:24:15 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/bptree.o
|
2010-09-04 20:26:23 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/ddt.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/ddt_zap.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dmu.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dmu_diff.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dmu_object.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dmu_objset.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dmu_send.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dmu_traverse.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dmu_tx.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dmu_zfetch.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dnode.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dnode_sync.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_dataset.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_deadlist.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_deleg.o
|
2013-12-11 22:33:41 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_bookmark.o
|
2010-09-04 20:26:23 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_dir.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_pool.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_prop.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_scan.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_synctask.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/fm.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/gzip.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/lzjb.o
|
2013-01-23 09:54:30 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/lz4.o
|
2010-09-04 20:26:23 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/metaslab.o
|
Illumos #4101, #4102, #4103, #4105, #4106
4101 metaslab_debug should allow for fine-grained control
4102 space_maps should store more information about themselves
4103 space map object blocksize should be increased
4105 removing a mirrored log device results in a leaked object
4106 asynchronously load metaslab
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed by: Adam Leventhal <ahl@delphix.com>
Reviewed by: Sebastien Roy <seb@delphix.com>
Approved by: Garrett D'Amore <garrett@damore.org>
Prior to this patch, space_maps were preferred solely based on the
amount of free space left in each. Unfortunately, this heuristic didn't
contain any information about the make-up of that free space, which
meant we could keep preferring and loading a highly fragmented space map
that wouldn't actually have enough contiguous space to satisfy the
allocation; then unloading that space_map and repeating the process.
This change modifies the space_map's to store additional information
about the contiguous space in the space_map, so that we can use this
information to make a better decision about which space_map to load.
This requires reallocating all space_map objects to increase their
bonus buffer size sizes enough to fit the new metadata.
The above feature can be enabled via a new feature flag introduced by
this change: com.delphix:spacemap_histogram
In addition to the above, this patch allows the space_map block size to
be increase. Currently the block size is set to be 4K in size, which has
certain implications including the following:
* 4K sector devices will not see any compression benefit
* large space_maps require more metadata on-disk
* large space_maps require more time to load (typically random reads)
Now the space_map block size can adjust as needed up to the maximum size
set via the space_map_max_blksz variable.
A bug was fixed which resulted in potentially leaking an object when
removing a mirrored log device. The previous logic for vdev_remove() did
not deal with removing top-level vdevs that are interior vdevs (i.e.
mirror) correctly. The problem would occur when removing a mirrored log
device, and result in the DTL space map object being leaked; because
top-level vdevs don't have DTL space map objects associated with them.
References:
https://www.illumos.org/issues/4101
https://www.illumos.org/issues/4102
https://www.illumos.org/issues/4103
https://www.illumos.org/issues/4105
https://www.illumos.org/issues/4106
https://github.com/illumos/illumos-gate/commit/0713e23
Porting notes:
A handful of kmem_alloc() calls were converted to kmem_zalloc(). Also,
the KM_PUSHPAGE and TQ_PUSHPAGE flags were used as necessary.
Ported-by: Tim Chase <tim@chase2k.com>
Signed-off-by: Prakash Surya <surya1@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #2488
2013-10-01 21:25:53 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/range_tree.o
|
2010-09-04 20:26:23 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/refcount.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/rrwlock.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/sa.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/sha256.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/spa.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/spa_boot.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/spa_config.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/spa_errlog.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/spa_history.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/spa_misc.o
|
Add visibility in to arc_read
This change is an attempt to add visibility into the arc_read calls
occurring on a system, in real time. To do this, a list was added to the
in memory SPA data structure for a pool, with each element on the list
corresponding to a call to arc_read. These entries are then exported
through the kstat interface, which can then be interpreted in userspace.
For each arc_read call, the following information is exported:
* A unique identifier (uint64_t)
* The time the entry was added to the list (hrtime_t)
(*not* wall clock time; relative to the other entries on the list)
* The objset ID (uint64_t)
* The object number (uint64_t)
* The indirection level (uint64_t)
* The block ID (uint64_t)
* The name of the function originating the arc_read call (char[24])
* The arc_flags from the arc_read call (uint32_t)
* The PID of the reading thread (pid_t)
* The command or name of thread originating read (char[16])
From this exported information one can see, in real time, exactly what
is being read, what function is generating the read, and whether or not
the read was found to be already cached.
There is still some work to be done, but this should serve as a good
starting point.
Specifically, dbuf_read's are not accounted for in the currently
exported information. Thus, a follow up patch should probably be added
to export these calls that never call into arc_read (they only hit the
dbuf hash table). In addition, it might be nice to create a utility
similar to "arcstat.py" to digest the exported information and display
it in a more readable format. Or perhaps, log the information and allow
for it to be "replayed" at a later time.
Signed-off-by: Prakash Surya <surya1@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
2013-09-06 23:09:05 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/spa_stats.o
|
2010-09-04 20:26:23 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/space_map.o
|
Illumos #4101, #4102, #4103, #4105, #4106
4101 metaslab_debug should allow for fine-grained control
4102 space_maps should store more information about themselves
4103 space map object blocksize should be increased
4105 removing a mirrored log device results in a leaked object
4106 asynchronously load metaslab
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed by: Adam Leventhal <ahl@delphix.com>
Reviewed by: Sebastien Roy <seb@delphix.com>
Approved by: Garrett D'Amore <garrett@damore.org>
Prior to this patch, space_maps were preferred solely based on the
amount of free space left in each. Unfortunately, this heuristic didn't
contain any information about the make-up of that free space, which
meant we could keep preferring and loading a highly fragmented space map
that wouldn't actually have enough contiguous space to satisfy the
allocation; then unloading that space_map and repeating the process.
This change modifies the space_map's to store additional information
about the contiguous space in the space_map, so that we can use this
information to make a better decision about which space_map to load.
This requires reallocating all space_map objects to increase their
bonus buffer size sizes enough to fit the new metadata.
The above feature can be enabled via a new feature flag introduced by
this change: com.delphix:spacemap_histogram
In addition to the above, this patch allows the space_map block size to
be increase. Currently the block size is set to be 4K in size, which has
certain implications including the following:
* 4K sector devices will not see any compression benefit
* large space_maps require more metadata on-disk
* large space_maps require more time to load (typically random reads)
Now the space_map block size can adjust as needed up to the maximum size
set via the space_map_max_blksz variable.
A bug was fixed which resulted in potentially leaking an object when
removing a mirrored log device. The previous logic for vdev_remove() did
not deal with removing top-level vdevs that are interior vdevs (i.e.
mirror) correctly. The problem would occur when removing a mirrored log
device, and result in the DTL space map object being leaked; because
top-level vdevs don't have DTL space map objects associated with them.
References:
https://www.illumos.org/issues/4101
https://www.illumos.org/issues/4102
https://www.illumos.org/issues/4103
https://www.illumos.org/issues/4105
https://www.illumos.org/issues/4106
https://github.com/illumos/illumos-gate/commit/0713e23
Porting notes:
A handful of kmem_alloc() calls were converted to kmem_zalloc(). Also,
the KM_PUSHPAGE and TQ_PUSHPAGE flags were used as necessary.
Ported-by: Tim Chase <tim@chase2k.com>
Signed-off-by: Prakash Surya <surya1@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #2488
2013-10-01 21:25:53 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/space_reftree.o
|
2010-09-04 20:26:23 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/txg.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/uberblock.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/unique.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/vdev.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/vdev_cache.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/vdev_disk.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/vdev_file.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/vdev_label.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/vdev_mirror.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/vdev_missing.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/vdev_queue.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/vdev_raidz.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/vdev_root.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zap.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zap_leaf.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zap_micro.o
|
2012-12-13 23:24:15 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfeature.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfeature_common.o
|
2010-09-04 20:26:23 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_acl.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_byteswap.o
|
2011-11-11 07:15:53 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_ctldir.o
|
2010-09-04 20:26:23 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_debug.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_dir.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_fm.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_fuid.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_ioctl.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_log.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_onexit.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_replay.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_rlock.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_sa.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_vfsops.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_vnops.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_znode.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zil.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zio.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zio_checksum.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zio_compress.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zio_inject.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zle.o
|
2011-11-11 07:15:53 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zpl_ctldir.o
|
2011-04-28 16:35:50 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zpl_export.o
|
2011-01-26 20:03:58 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zpl_file.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zpl_inode.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zpl_super.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zpl_xattr.o
|
2010-09-04 20:26:23 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zrlock.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zvol.o
|
2013-09-04 12:00:57 +00:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_destroy.o
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_userhold.o
|