/linux-4.4.14/Documentation/device-mapper/ |
D | snapshot.txt | 1 Device-mapper snapshot support 11 *) To merge a snapshot of a block device back into the snapshot's origin 18 For snapshot merge the contents of the COW storage are merged back into 23 snapshot, snapshot-origin, and snapshot-merge. 25 *) snapshot-origin <origin> 29 original data will be saved in the <COW device> of each snapshot to keep 33 *) snapshot <origin> <COW device> <persistent?> <chunksize> 35 A snapshot of the <origin> block device is created. Changed chunks of 39 smaller than the origin and if it fills up the snapshot will become 46 snapshot status. So supported store types are "P", "PO" and "N". [all …]
|
D | era.txt | 12 coherency after rolling back a vendor snapshot. 44 Drop the metadata snapshot. 65 snapshot was the primary use case when developing this target: 67 Taking a vendor snapshot 72 - Take vendor snapshot (the era and snapshot should be forever 75 Rolling back to an vendor snapshot 80 - Take metadata snapshot 81 - Ascertain which blocks have been written since the snapshot was taken
|
D | zero.txt | 11 conjunction with dm-snapshot. A sparse device reports a device-size larger 26 Then create a snapshot of the zero device, using any available block-device as 31 echo "0 $TEN_TERABYTES snapshot /dev/mapper/zero1 /dev/sdb1 p 128" | \
|
D | thin-provisioning.txt | 173 i) Creating an internal snapshot. 177 N.B. If the origin device that you wish to snapshot is active, you 178 must suspend it before creating the snapshot to avoid corruption. 188 ii) Using an internal snapshot. 191 between the origin and the snapshot. Indeed the snapshot is no 218 i) Creating a snapshot of an external device 225 ii) Using a snapshot of an external device. 231 N.B. All descendants (internal snapshots) of this snapshot require the 334 Create a new snapshot of another thinly-provisioned device. 338 of which the new device will be a snapshot. [all …]
|
D | kcopyd.txt | 6 notification. It is used by dm-snapshot and dm-mirror.
|
D | persistent-data.txt | 11 - Another multi-snapshot target based on a design of Daniel Phillips
|
/linux-4.4.14/Documentation/power/ |
D | userland-swsusp.txt | 10 utilities that will read/write the system memory snapshot from/to the 19 be read from /sys/class/misc/snapshot/dev. 39 SNAPSHOT_CREATE_IMAGE - create a snapshot of the system memory; the 42 creating the snapshot (1) or after restoring the system memory state 44 SNAPSHOT_CREATE_IMAGE ioctl() again); after the snapshot 49 uploaded snapshot image; before calling it you should transfer 50 the system memory snapshot back to the kernel using the write() 51 operation; this call will not succeed if the snapshot 54 SNAPSHOT_FREE - free memory allocated for the snapshot image 99 The device's read() operation can be used to transfer the snapshot image from [all …]
|
D | swsusp.txt | 243 with state snapshot 245 state snapshot: copy of whole used memory is taken with interrupts disabled
|
D | devices.txt | 503 image forms an atomic snapshot of the system state.
|
/linux-4.4.14/kernel/power/ |
D | swap.c | 514 struct snapshot_handle *snapshot, in save_image() argument 535 ret = snapshot_read_next(snapshot); in save_image() 538 ret = swap_write_page(handle, data_of(*snapshot), &hb); in save_image() 650 struct snapshot_handle *snapshot, in save_image_lzo() argument 757 ret = snapshot_read_next(snapshot); in save_image_lzo() 765 data_of(*snapshot), PAGE_SIZE); in save_image_lzo() 892 struct snapshot_handle snapshot; in swsusp_write() local 910 memset(&snapshot, 0, sizeof(struct snapshot_handle)); in swsusp_write() 911 error = snapshot_read_next(&snapshot); in swsusp_write() 918 header = (struct swsusp_info *)data_of(snapshot); in swsusp_write() [all …]
|
D | Makefile | 10 obj-$(CONFIG_HIBERNATION) += hibernate.o snapshot.o swap.o user.o
|
/linux-4.4.14/arch/x86/kernel/cpu/ |
D | perf_event_intel_bts.c | 54 bool snapshot; member 101 buf->snapshot = overwrite; in bts_buffer_setup_aux() 145 if (!buf->snapshot) { in bts_config_buffer() 162 ds->bts_interrupt_threshold = !buf->snapshot in bts_config_buffer() 176 if (buf->snapshot) in bts_buffer_is_full() 199 if (!buf->snapshot) { in bts_update() 228 if (!buf->snapshot) in __bts_event_start() 307 if (buf->snapshot) in bts_buffer_reset() 394 if (!buf || buf->snapshot) in intel_bts_interrupt() 427 if (buf->snapshot) in bts_event_del()
|
D | perf_event_intel_pt.c | 454 if (!buf->snapshot && !pt_cap_get(PT_CAP_topa_multiple_entries)) { in topa_insert_pages() 536 if (buf->snapshot) { in pt_update_head() 603 if (!pt_cap_get(PT_CAP_topa_multiple_entries) && !buf->snapshot && in pt_handle_status() 782 if (buf->snapshot) in pt_buffer_reset_offsets() 865 pt_buffer_setup_aux(int cpu, void **pages, int nr_pages, bool snapshot) in pt_buffer_setup_aux() argument 883 buf->snapshot = snapshot; in pt_buffer_setup_aux() 920 if (buf->snapshot) in pt_buffer_is_full() 1052 if (buf->snapshot) in pt_event_del() 1077 if (!buf->snapshot) { in pt_event_add()
|
D | intel_pt.h | 100 bool snapshot; member
|
D | perf_event_intel_cqm.c | 1146 EVENT_ATTR_STR(llc_occupancy.snapshot, intel_cqm_llc_snapshot, "1");
|
/linux-4.4.14/fs/nilfs2/ |
D | sysfs.h | 98 NILFS_CP_ATTR_STRUCT(snapshot); 141 NILFS_INFO_ATTR(snapshot, name) 143 NILFS_RO_ATTR(snapshot, name) 145 NILFS_RW_ATTR(snapshot, name)
|
D | Kconfig | 17 snapshot is mountable as a read-only file system concurrently with
|
/linux-4.4.14/tools/perf/util/ |
D | pmu.h | 34 bool snapshot; member 46 bool snapshot; member
|
D | pmu.c | 204 alias->snapshot = true; in perf_pmu__parse_snapshot() 826 (info->snapshot && alias->snapshot)) in check_info_data() 835 if (alias->snapshot) in check_info_data() 836 info->snapshot = alias->snapshot; in check_info_data() 860 info->snapshot = false; in perf_pmu__check_alias()
|
D | stat.c | 263 if (!evsel->snapshot) in process_counter_values() 324 if (!counter->snapshot) in perf_stat_process_counter()
|
D | auxtrace.c | 1152 bool snapshot, size_t snapshot_size) in __auxtrace_mmap__read() argument 1160 if (snapshot) { in __auxtrace_mmap__read() 1188 if (snapshot && size > snapshot_size) in __auxtrace_mmap__read() 1245 if (!snapshot) { in __auxtrace_mmap__read()
|
D | evsel.h | 108 bool snapshot; member
|
D | parse-events.c | 1033 evsel->snapshot = info.snapshot; in parse_events_add_pmu()
|
/linux-4.4.14/Documentation/filesystems/ |
D | nilfs2.txt | 18 full. Each snapshot is mountable as a read-only file system 57 cp=n Specify the checkpoint-number of the snapshot to be 59 user command. Only the checkpoints marked as snapshot 94 checkpoint and snapshot state. This ioctl is 161 mkcp make a checkpoint or a snapshot. 162 chcp change an existing checkpoint to a snapshot or vice versa. 165 To mount a snapshot, 169 where <cno> is the checkpoint number of the snapshot. 171 To unmount the NILFS2 mount point or snapshot, simply:
|
D | qnx6.txt | 38 In write mode with reach new snapshot (after each synchronous write), the 41 So basically the snapshot functionality is realized by an atomic final 164 The rational behind that is that a write request can work on a new snapshot
|
D | path-lookup.txt | 184 dentry seqlock (d_seq) is used to take a "coherent snapshot" of what the dentry 185 looks like (its name, parent, and inode). That snapshot is then used to start 186 the next part of the path walk. When loading the coherent snapshot under d_seq, 226 path string, rcu-walk uses a d_seq protected snapshot. When looking up a 227 child of this parent snapshot, we open d_seq critical section on the child 278 parent snapshot fails, the house comes down, because we had closed the d_seq
|
D | ceph.txt | 53 Ceph includes flexible snapshot mechanism that allows a user to create 54 a snapshot on any subdirectory (and its nested contents) in the
|
D | btrfs.txt | 126 operations). This was previously the behavior only when a snapshot is
|
D | xfs.txt | 176 system uuid. This is useful to mount LVM snapshot volumes,
|
D | proc.txt | 207 snapshot of a moment, you can see /proc/<pid>/smaps file and scan page table.
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-bus-rbd | 13 The snapshot name can be "-" or omitted to map the image read/write. A <dev-id> 14 will be assigned for any registered block device. If snapshot is used, it will 93 The current snapshot for which the device is mapped.
|
D | sysfs-devices | 5 The /sys/devices tree contains a snapshot of the
|
D | sysfs-fs-nilfs2 | 256 Show number of inodes for snapshot. 262 Show number of blocks for snapshot.
|
D | sysfs-class-devfreq | 72 This is a snapshot of available frequencies and not limited
|
D | sysfs-devices-memory | 5 The /sys/devices/system/memory contains a snapshot of the
|
D | sysfs-kernel-slab | 7 The /sys/kernel/slab directory contains a snapshot of the
|
/linux-4.4.14/drivers/misc/echo/ |
D | echo.c | 265 ec->snapshot = kcalloc(ec->taps, sizeof(int16_t), GFP_KERNEL); in oslec_create() 266 if (!ec->snapshot) in oslec_create() 302 kfree(ec->snapshot); in oslec_free() 341 memcpy(ec->snapshot, ec->fir_taps16[0], ec->taps * sizeof(int16_t)); in oslec_snapshot()
|
D | echo.h | 184 int16_t *snapshot; member
|
/linux-4.4.14/fs/qnx6/ |
D | README | 2 This is a snapshot of the QNX6 filesystem for Linux.
|
/linux-4.4.14/fs/qnx4/ |
D | README | 2 This is a snapshot of the QNX4 filesystem for Linux.
|
/linux-4.4.14/net/ceph/ |
D | Makefile | 14 pagevec.o snapshot.o
|
/linux-4.4.14/tools/perf/Documentation/ |
D | intel-pt.txt | 112 data captured is to use 'snapshot' mode which is explained further below. 113 Refer to 'new snapshot option' and 'Intel PT modes of operation' further below. 368 new snapshot option 371 The difference between full trace and snapshot from the kernel's perspective is 373 yet (and indicated that by advancing aux_tail), whereas in snapshot mode we let 375 interesting happens, we can stop it and grab a snapshot of what was going on 378 To select snapshot mode a new option has been added: 382 Optionally it can be followed by the snapshot size e.g. 386 The default snapshot size is the auxtrace mmap size. If neither auxtrace mmap size 387 nor snapshot size is specified, then the default is 4MiB for privileged users [all …]
|
D | intel-bts.txt | 36 snapshot option 39 The snapshot option is the same as Intel PT (refer Intel PT documentation).
|
D | perf-record.txt | 302 --snapshot:: 305 snapshot can be specified. In Snapshot Mode, trace data is captured only when
|
/linux-4.4.14/drivers/md/ |
D | Makefile | 8 dm-snapshot-y += dm-snap.o dm-exception-store.o dm-snap-transient.o \ 48 obj-$(CONFIG_DM_SNAPSHOT) += dm-snapshot.o
|
/linux-4.4.14/Documentation/video4linux/ |
D | meye.txt | 113 Takes a snapshot in an uncompressed or compressed jpeg format. 114 This ioctl blocks until the snapshot is done and returns (for 115 jpeg snapshot) the size of the image. The image data is
|
D | README.ir | 11 from http://bytesex.org/snapshot/input-<date>.tar.gz
|
D | README.cx88 | 47 (1) Try upgrading to the latest snapshot, maybe it has been added
|
D | README.pvrusb2 | 18 last known snapshot and evolved the driver to the state it is in 143 in the standalone snapshot).
|
/linux-4.4.14/Documentation/trace/ |
D | events.txt | 456 - snapshot 458 This command causes a snapshot to be triggered whenever the 461 The following command creates a snapshot every time a block request 463 events or functions at the time, the snapshot trace buffer would 466 # echo 'snapshot if nr_rq > 1' > \ 469 To only snapshot once: 471 # echo 'snapshot:1 if nr_rq > 1' > \ 476 # echo '!snapshot if nr_rq > 1' > \ 479 # echo '!snapshot:1 if nr_rq > 1' > \ 482 Note that there can be only one snapshot trigger per triggering
|
D | ftrace.txt | 296 snapshot: 298 This displays the "snapshot" buffer and also lets the user 299 take a snapshot of the current running trace. 457 per_cpu/cpu0/snapshot: 459 This is similar to the main "snapshot" file, but will only 460 snapshot the current CPU (if supported). It only displays 461 the content of the snapshot for a given CPU, and if 467 from the snapshot buffer for the given CPU. 2025 system clock since it started. A snapshot of this time is 2487 - snapshot [all …]
|
/linux-4.4.14/arch/parisc/math-emu/ |
D | README | 10 in any way. This copy of this snapshot is no longer the property
|
/linux-4.4.14/drivers/media/usb/pwc/ |
D | Kconfig | 45 This option makes USB Philips cameras register the snapshot button as
|
/linux-4.4.14/kernel/trace/ |
D | Kconfig | 242 bool "Create a snapshot trace buffer" 245 Allow tracing users to take snapshot of the current buffer using the 248 echo 1 > /sys/kernel/debug/tracing/snapshot 249 cat snapshot 252 bool "Allow snapshot to swap per CPU" 256 Allow doing a snapshot of a single CPU buffer instead of a 260 echo 1 > /sys/kernel/debug/tracing/per_cpu/cpu2/snapshot
|
D | trace.c | 2472 if (iter->snapshot && iter->trace->use_max_tr) in s_start() 2476 if (!iter->snapshot) in s_start() 2517 if (iter->snapshot && iter->trace->use_max_tr) in s_stop() 2521 if (!iter->snapshot) in s_stop() 2980 if (iter->snapshot && trace_empty(iter)) in s_show() 3032 __tracing_open(struct inode *inode, struct file *file, bool snapshot) in __tracing_open() argument 3068 if (tr->current_trace->print_max || snapshot) in __tracing_open() 3073 iter->snapshot = snapshot; in __tracing_open() 3091 if (!iter->snapshot) in __tracing_open() 3183 if (!iter->snapshot) in tracing_release() [all …]
|
/linux-4.4.14/include/linux/ |
D | nilfs2_fs.h | 557 NILFS_CHECKPOINT_FNS(SNAPSHOT, snapshot) 590 NILFS_CPINFO_FNS(SNAPSHOT, snapshot)
|
D | trace_events.h | 94 bool snapshot; member
|
/linux-4.4.14/Documentation/sound/alsa/ |
D | timestamping.txt | 3 - Trigger_tstamp is the system time snapshot taken when the .trigger 4 callback is invoked. This snapshot is taken by the ALSA core in the 30 along with a snapshot of system time. Applications can select from
|
D | HD-Audio.txt | 660 way to try the latest ALSA code is to build from the snapshot 661 tarball. There are daily tarballs and the latest snapshot tarball. 664 install(-modules). See INSTALL in the package. The snapshot tarballs 667 - ftp://ftp.suse.com/pub/people/tiwai/snapshot/
|
/linux-4.4.14/drivers/scsi/isci/ |
D | scu_task_context.h | 866 struct transport_snapshot snapshot; /* read only set to 0 */ member
|
/linux-4.4.14/Documentation/block/ |
D | stat.txt | 12 represent a consistent snapshot of the state of the device. If the
|
/linux-4.4.14/Documentation/ko_KR/ |
D | HOWTO | 289 커널 트리의 snapshot 들이 있다. 이 패치들은 일반적으로 날마다 배포되며
|
/linux-4.4.14/arch/powerpc/boot/dts/ |
D | acadia.dts | 176 * that it uses to generate snapshot triggers. We
|
/linux-4.4.14/Documentation/ |
D | gdb-kernel-debugging.txt | 147 this is just a snapshot of the initial version:
|
D | rfkill.txt | 100 userspace is able to get a consistent snapshot of all rfkill devices in the
|
D | iostats.txt | 40 each snapshot of your disk statistics.
|
D | devices.txt | 448 231 = /dev/snapshot System memory snapshot device
|
D | kernel-parameters.txt | 425 Allocate the ftrace snapshot buffer on boot up when the
|
/linux-4.4.14/Documentation/networking/ |
D | README.ipw2200 | 169 of the ipw2200 development snapshot releases available from the 403 development snapshot releases.
|
/linux-4.4.14/drivers/net/wireless/ipw2x00/ |
D | ipw2100.c | 2326 #define SNAPSHOT_ADDR(ofs) (priv->snapshot[((ofs) >> 12) & 0xff] + ((ofs) & 0xfff)) 2330 if (!priv->snapshot[0]) in ipw2100_snapshot_free() 2333 kfree(priv->snapshot[i]); in ipw2100_snapshot_free() 2334 priv->snapshot[0] = NULL; in ipw2100_snapshot_free() 2341 if (priv->snapshot[0]) in ipw2100_snapshot_alloc() 2344 priv->snapshot[i] = kmalloc(0x1000, GFP_ATOMIC); in ipw2100_snapshot_alloc() 2345 if (!priv->snapshot[i]) { in ipw2100_snapshot_alloc() 2349 kfree(priv->snapshot[--i]); in ipw2100_snapshot_alloc() 2350 priv->snapshot[0] = NULL; in ipw2100_snapshot_alloc() 3878 if (priv->snapshot[0]) in show_memory() [all …]
|
D | ipw2100.h | 516 u8 *snapshot[0x30]; member
|
/linux-4.4.14/Documentation/ABI/stable/ |
D | sysfs-class-tpm | 93 for a snapshot in time.
|
/linux-4.4.14/mm/ |
D | page-writeback.c | 1330 goto snapshot; in __wb_update_bandwidth() 1347 snapshot: in __wb_update_bandwidth()
|
/linux-4.4.14/Documentation/fb/ |
D | framebuffer.txt | 45 read and write their contents. You can, for example, make a screen snapshot by
|
/linux-4.4.14/drivers/scsi/aic7xxx/ |
D | aic79xx.seq | 1486 * that a FIFO will be freed to handle snapshot requests for 1879 * Switch to the active FIFO after clearing the snapshot 1910 * The first is a snapshot save pointers where the current FIFO is not 1911 * active and contains a snapshot of the current poniter information. 1916 * of snapshot is not active.
|
/linux-4.4.14/Documentation/development-process/ |
D | 2.Process | 285 Stephen Rothwell. The linux-next tree is, by design, a snapshot of what
|
/linux-4.4.14/Documentation/sysctl/ |
D | vm.txt | 699 why oom happens. You can get snapshot.
|
/linux-4.4.14/Documentation/RCU/ |
D | RTFP.txt | 2160 readers to confine themselves to the desired snapshot of the 2571 readers to confine themselves to the desired snapshot of the
|