2010-08-26 22:22:58 +04:00
|
|
|
MODULE := zfs
|
|
|
|
|
|
2012-07-09 13:23:00 +04:00
|
|
|
EXTRA_CFLAGS = $(ZFS_MODULE_CFLAGS) @KERNELCPPFLAGS@
|
2010-08-26 22:22:58 +04:00
|
|
|
|
2012-07-09 13:23:00 +04:00
|
|
|
obj-$(CONFIG_ZFS) := $(MODULE).o
|
2010-08-26 22:22:58 +04:00
|
|
|
|
2010-09-05 00:26:23 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/arc.o
|
2014-06-06 01:19:08 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/blkptr.o
|
2010-09-05 00:26:23 +04: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 04:11:19 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dbuf_stats.o
|
2012-12-14 03:24:15 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/bptree.o
|
2010-09-05 00:26:23 +04: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-12 02:33:41 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_bookmark.o
|
2010-09-05 00:26:23 +04: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 13:54:30 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/lz4.o
|
2010-09-05 00:26:23 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/metaslab.o
|
2015-01-13 06:52:19 +03:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/multilist.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-02 01:25:53 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/range_tree.o
|
2010-09-05 00:26:23 +04: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-07 03:09:05 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/spa_stats.o
|
2010-09-05 00:26:23 +04: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-02 01:25:53 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/space_reftree.o
|
2010-09-05 00:26:23 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/txg.o
|
Swap DTRACE_PROBE* with Linux tracepoints
This patch leverages Linux tracepoints from within the ZFS on Linux
code base. It also refactors the debug code to bring it back in sync
with Illumos.
The information exported via tracepoints can be used for a variety of
reasons (e.g. debugging, tuning, general exploration/understanding,
etc). It is advantageous to use Linux tracepoints as the mechanism to
export this kind of information (as opposed to something else) for a
number of reasons:
* A number of external tools can make use of our tracepoints
"automatically" (e.g. perf, systemtap)
* Tracepoints are designed to be extremely cheap when disabled
* It's one of the "accepted" ways to export this kind of
information; many other kernel subsystems use tracepoints too.
Unfortunately, though, there are a few caveats as well:
* Linux tracepoints appear to only be available to GPL licensed
modules due to the way certain kernel functions are exported.
Thus, to actually make use of the tracepoints introduced by this
patch, one might have to patch and re-compile the kernel;
exporting the necessary functions to non-GPL modules.
* Prior to upstream kernel version v3.14-rc6-30-g66cc69e, Linux
tracepoints are not available for unsigned kernel modules
(tracepoints will get disabled due to the module's 'F' taint).
Thus, one either has to sign the zfs kernel module prior to
loading it, or use a kernel versioned v3.14-rc6-30-g66cc69e or
newer.
Assuming the above two requirements are satisfied, lets look at an
example of how this patch can be used and what information it exposes
(all commands run as 'root'):
# list all zfs tracepoints available
$ ls /sys/kernel/debug/tracing/events/zfs
enable filter zfs_arc__delete
zfs_arc__evict zfs_arc__hit zfs_arc__miss
zfs_l2arc__evict zfs_l2arc__hit zfs_l2arc__iodone
zfs_l2arc__miss zfs_l2arc__read zfs_l2arc__write
zfs_new_state__mfu zfs_new_state__mru
# enable all zfs tracepoints, clear the tracepoint ring buffer
$ echo 1 > /sys/kernel/debug/tracing/events/zfs/enable
$ echo 0 > /sys/kernel/debug/tracing/trace
# import zpool called 'tank', inspect tracepoint data (each line was
# truncated, they're too long for a commit message otherwise)
$ zpool import tank
$ cat /sys/kernel/debug/tracing/trace | head -n35
# tracer: nop
#
# entries-in-buffer/entries-written: 1219/1219 #P:8
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
lt-zpool-30132 [003] .... 91344.200050: zfs_arc__miss: hdr...
z_rd_int/0-30156 [003] .... 91344.200611: zfs_new_state__mru...
lt-zpool-30132 [003] .... 91344.201173: zfs_arc__miss: hdr...
z_rd_int/1-30157 [003] .... 91344.201756: zfs_new_state__mru...
lt-zpool-30132 [003] .... 91344.201795: zfs_arc__miss: hdr...
z_rd_int/2-30158 [003] .... 91344.202099: zfs_new_state__mru...
lt-zpool-30132 [003] .... 91344.202126: zfs_arc__hit: hdr ...
lt-zpool-30132 [003] .... 91344.202130: zfs_arc__hit: hdr ...
lt-zpool-30132 [003] .... 91344.202134: zfs_arc__hit: hdr ...
lt-zpool-30132 [003] .... 91344.202146: zfs_arc__miss: hdr...
z_rd_int/3-30159 [003] .... 91344.202457: zfs_new_state__mru...
lt-zpool-30132 [003] .... 91344.202484: zfs_arc__miss: hdr...
z_rd_int/4-30160 [003] .... 91344.202866: zfs_new_state__mru...
lt-zpool-30132 [003] .... 91344.202891: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.203034: zfs_arc__miss: hdr...
z_rd_iss/1-30149 [001] .... 91344.203749: zfs_new_state__mru...
lt-zpool-30132 [001] .... 91344.203789: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.203878: zfs_arc__miss: hdr...
z_rd_iss/3-30151 [001] .... 91344.204315: zfs_new_state__mru...
lt-zpool-30132 [001] .... 91344.204332: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.204337: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.204352: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.204356: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.204360: zfs_arc__hit: hdr ...
To highlight the kind of detailed information that is being exported
using this infrastructure, I've taken the first tracepoint line from the
output above and reformatted it such that it fits in 80 columns:
lt-zpool-30132 [003] .... 91344.200050: zfs_arc__miss:
hdr {
dva 0x1:0x40082
birth 15491
cksum0 0x163edbff3a
flags 0x640
datacnt 1
type 1
size 2048
spa 3133524293419867460
state_type 0
access 0
mru_hits 0
mru_ghost_hits 0
mfu_hits 0
mfu_ghost_hits 0
l2_hits 0
refcount 1
} bp {
dva0 0x1:0x40082
dva1 0x1:0x3000e5
dva2 0x1:0x5a006e
cksum 0x163edbff3a:0x75af30b3dd6:0x1499263ff5f2b:0x288bd118815e00
lsize 2048
} zb {
objset 0
object 0
level -1
blkid 0
}
For the specific tracepoint shown here, 'zfs_arc__miss', data is
exported detailing the arc_buf_hdr_t (hdr), blkptr_t (bp), and
zbookmark_t (zb) that caused the ARC miss (down to the exact DVA!).
This kind of precise and detailed information can be extremely valuable
when trying to answer certain kinds of questions.
For anybody unfamiliar but looking to build on this, I found the XFS
source code along with the following three web links to be extremely
helpful:
* http://lwn.net/Articles/379903/
* http://lwn.net/Articles/381064/
* http://lwn.net/Articles/383362/
I should also node the more "boring" aspects of this patch:
* The ZFS_LINUX_COMPILE_IFELSE autoconf macro was modified to
support a sixth paramter. This parameter is used to populate the
contents of the new conftest.h file. If no sixth parameter is
provided, conftest.h will be empty.
* The ZFS_LINUX_TRY_COMPILE_HEADER autoconf macro was introduced.
This macro is nearly identical to the ZFS_LINUX_TRY_COMPILE macro,
except it has support for a fifth option that is then passed as
the sixth parameter to ZFS_LINUX_COMPILE_IFELSE.
These autoconf changes were needed to test the availability of the Linux
tracepoint macros. Due to the odd nature of the Linux tracepoint macro
API, a separate ".h" must be created (the path and filename is used
internally by the kernel's define_trace.h file).
* The HAVE_DECLARE_EVENT_CLASS autoconf macro was introduced. This
is to determine if we can safely enable the Linux tracepoint
functionality. We need to selectively disable the tracepoint code
due to the kernel exporting certain functions as GPL only. Without
this check, the build process will fail at link time.
In addition, the SET_ERROR macro was modified into a tracepoint as well.
To do this, the 'sdt.h' file was moved into the 'include/sys' directory
and now contains a userspace portion and a kernel space portion. The
dprintf and zfs_dbgmsg* interfaces are now implemented as tracepoint as
well.
Signed-off-by: Prakash Surya <surya1@llnl.gov>
Signed-off-by: Ned Bass <bass6@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
2014-06-13 21:54:48 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/trace.o
|
2010-09-05 00:26:23 +04:00
|
|
|
$(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-14 03:24:15 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfeature.o
|
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfeature_common.o
|
2010-09-05 00:26:23 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_acl.o
|
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_byteswap.o
|
2011-11-11 11:15:53 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zfs_ctldir.o
|
2010-09-05 00:26:23 +04: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 11:15:53 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zpl_ctldir.o
|
2011-04-28 20:35:50 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zpl_export.o
|
2011-01-26 23:03:58 +03: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-05 00:26:23 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zrlock.o
|
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/zvol.o
|
2013-09-04 16:00:57 +04:00
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_destroy.o
|
|
|
|
|
$(MODULE)-objs += @top_srcdir@/module/zfs/dsl_userhold.o
|