Home
last modified time | relevance | path

Searched full:discard (Results 1 – 25 of 871) sorted by relevance

12345678910>>...35

/linux/fs/btrfs/
H A Ddiscard.c12 #include "discard.h"
17 * This contains the logic to handle async discard.
19 * Async discard manages trimming of free space outside of transaction commit.
24 * passes with different discard filter requirements. A delayed work item is
39 * The in-memory free space cache serves as the backing state for discard.
45 * ease/efficiency for find_free_extent() and the accuracy of discard state.
52 * tradeoff between discard state accuracy and the cost of accounting.
77 * Determine if async discard should be running.
79 * @discard_ctl: discard control
171 * If the block group is currently running in the discard workfn, we in remove_from_discard_list()
[all …]
/linux/arch/arc/kernel/
H A Dvmlinux.lds.S119 /DISCARD/ : { *(.eh_frame) }
135 /DISCARD/ : { *(.debug_frame) }
136 /DISCARD/ : { *(.debug_aranges) }
137 /DISCARD/ : { *(.debug_pubnames) }
138 /DISCARD/ : { *(.debug_info) }
139 /DISCARD/ : { *(.debug_abbrev) }
140 /DISCARD/ : { *(.debug_line) }
141 /DISCARD/ : { *(.debug_str) }
142 /DISCARD/ : { *(.debug_loc) }
143 /DISCARD/ : { *(.debug_macinfo) }
[all …]
/linux/include/xen/interface/io/
H A Dblkif.h111 * Recognised only if "feature-discard" is present in backend xenbus info.
112 * The "feature-discard" node contains a boolean indicating whether trim
113 * (ATA) or unmap (SCSI) - conviently called discard requests are likely
114 * to succeed or fail. Either way, a discard request
117 * or not it is worthwhile for the frontend to attempt discard requests.
119 * create the "feature-discard" node!
121 * Discard operation is a request for the underlying block device to mark
122 * extents to be erased. However, discard does not guarantee that the blocks
126 * Discard operations are passed with sector_number as the
127 * sector index to begin discard operations at and nr_sectors as the number of
[all …]
/linux/fs/xfs/
H A Dxfs_discard.c38 * extremely slow discard implementations (e.g. ceph RBD) and so walking a
52 * state of the free extent is out of our control and we cannot run a discard
54 * extent as busy and undergoing a discard operation whilst we held the AGF
57 * This is exactly how online discard works - free extents are marked busy when
59 * the busy extent record is marked as "undergoing discard" and the discard is
60 * then issued on the free extent. Once the discard completes, the busy extent
63 * In the context of fstrim, if we find a free extent we need to discard, we
64 * don't have to discard it immediately. All we need to do it record that free
65 * extent as being busy and under discard, and all the allocation routines will
67 * the AGF lock, we can safely discard it without holding the AGF lock because
[all …]
/linux/Documentation/block/
H A Dstat.rst40 discard I/Os requests number of discard I/Os processed
41 discard merges requests number of discard I/Os merged with in-queue I/O
42 discard sectors sectors number of sectors discarded
43 discard ticks milliseconds total wait time for discard requests
48 read I/Os, write I/Os, discard I/0s
61 read merges, write merges, discard merges
75 read ticks, write ticks, discard ticks, flush ticks
/linux/Documentation/admin-guide/
H A Djfs.rst52 discard=minlen, discard/nodiscard(*)
53 This enables/disables the use of discard/TRIM commands.
54 The discard/TRIM commands are sent to the underlying
60 When no value is given to the discard option, it defaults to
62 The minlen value of discard overrides the minlen value given
/linux/drivers/block/drbd/
H A Ddrbd_protocol.h60 /* REQ_OP_DISCARD. We used "discard" in different contexts before,
193 /* supports TRIM/DISCARD on the "wire" protocol */
196 /* Detect all-zeros during resync, and rather TRIM/UNMAP/DISCARD those blocks
204 * max discard size of 128 MiB
213 * We used to map that to "discard" on the sending side, and if we cannot
214 * guarantee that discard zeroes data, the receiving side would map discard
229 * If we cannot distinguish between zero-out and discard on the receiving
234 * unmap/trim/discard/de-allocate.
238 * or if we want to put the emphasis on discard, and only do a "best effort
239 * zeroing" (by "discarding" blocks aligned to discard-granularity, and zeroing
[all …]
/linux/include/uapi/linux/
H A Dvirtio_blk.h41 #define VIRTIO_BLK_F_DISCARD 13 /* DISCARD is supported */
96 * The maximum discard sectors (in 512-byte sectors) for
101 * The maximum number of discard segments in a
102 * discard command.
105 /* Discard commands must be aligned to this number of sectors. */
179 /* Discard command */
297 /* Discard/write zeroes range for each request. */
299 /* discard/write zeroes start sector */
301 /* number of discard/write zeroes sectors */
/linux/drivers/misc/mei/
H A Dinterrupt.c60 * mei_irq_discard_msg - discard received message
64 * @discard_len: the length of the message to discard (excluding header)
119 goto discard; in mei_cl_irq_read_msg()
123 goto discard; in mei_cl_irq_read_msg()
139 goto discard; in mei_cl_irq_read_msg()
156 goto discard; in mei_cl_irq_read_msg()
166 goto discard; in mei_cl_irq_read_msg()
177 goto discard; in mei_cl_irq_read_msg()
183 goto discard; in mei_cl_irq_read_msg()
188 goto discard; in mei_cl_irq_read_msg()
[all …]
/linux/Documentation/bpf/
H A Dringbuf.rst93 discarded. Discard is similar to commit, but makes consumer ignore the
112 The difference between commit and discard is very small. Discard just marks
114 code. Discard is useful for some advanced use-cases, such as ensuring
120 impossible to reserve a record, but forget to submit (or discard) it.
137 ``BPF_RB_NO_WAKEUP``/``BPF_RB_FORCE_WAKEUP`` flags for output/commit/discard
168 record is still being worked on, and discard bit, which might be set at commit
204 notifications, commit/discard/output helpers accept ``BPF_RB_NO_WAKEUP`` and
/linux/net/wireless/
H A Dwext-proc.c62 stats->discard.nwid, stats->discard.code, in wireless_seq_printf_stats()
63 stats->discard.fragment, stats->discard.retries, in wireless_seq_printf_stats()
64 stats->discard.misc, stats->miss.beacon); in wireless_seq_printf_stats()
/linux/net/dccp/
H A Dinput.c299 goto discard; in __dccp_rcv_established()
314 goto discard; in __dccp_rcv_established()
318 goto discard; in __dccp_rcv_established()
355 goto discard; in __dccp_rcv_established()
359 discard: in __dccp_rcv_established()
368 goto discard; in dccp_rcv_established()
377 discard: in dccp_rcv_established()
618 goto discard; in dccp_rcv_state_process()
630 goto discard; in dccp_rcv_state_process()
646 goto discard; in dccp_rcv_state_process()
[all …]
/linux/drivers/block/xen-blkback/
H A Dblkback.c977 preq.sector_number = req->u.discard.sector_number; in dispatch_discard_io()
978 preq.nr_sects = req->u.discard.nr_sectors; in dispatch_discard_io()
982 pr_warn("access denied: DISCARD [%llu->%llu] on dev=%04x\n", in dispatch_discard_io()
990 (req->u.discard.flag & BLKIF_DISCARD_SECURE)) in dispatch_discard_io()
992 req->u.discard.sector_number, in dispatch_discard_io()
993 req->u.discard.nr_sectors, GFP_KERNEL); in dispatch_discard_io()
995 err = blkdev_issue_discard(bdev, req->u.discard.sector_number, in dispatch_discard_io()
996 req->u.discard.nr_sectors, GFP_KERNEL); in dispatch_discard_io()
1000 pr_debug("discard op failed, not supported\n"); in dispatch_discard_io()
1005 make_response(ring, req->u.discard in dispatch_discard_io()
[all...]
/linux/block/
H A Dblk-lib.c25 * Make sure subsequent bios start aligned to the discard granularity if in bio_discard_limit()
32 * Align the bio size to the discard granularity to make splitting the bio in bio_discard_limit()
33 * at discard granularity boundaries easier in the driver if needed. in bio_discard_limit()
76 * blkdev_issue_discard - queue a discard
77 * @bdev: blockdev to issue discard for
79 * @nr_sects: number of sectors to discard
83 * Issue a discard request for the sectors in question.
/linux/arch/mips/include/asm/
H A Dyamon-dt.h16 * @discard: Length of additional memory to discard after the region.
21 phys_addr_t discard; member
/linux/include/uapi/asm-generic/
H A Dtermbits-common.h62 #define TCIFLUSH 0 /* Discard data received but not yet read */
63 #define TCOFLUSH 1 /* Discard data written but not yet sent */
64 #define TCIOFLUSH 2 /* Discard all pending data */
/linux/scripts/
H A Dmodule.lds.S15 /DISCARD/ : {
16 *(.discard)
17 *(.discard.*)
/linux/arch/sparc/vdso/
H A Dvdso-layout.lds.S76 /DISCARD/ : {
77 *(.discard)
78 *(.discard.*)
/linux/arch/arm64/kernel/vdso/
H A Dvdso.lds.S39 * Discard .note.gnu.property sections which are unused and have
42 /DISCARD/ : {
80 /DISCARD/ : {
/linux/Documentation/admin-guide/device-mapper/
H A Dlog-writes.rst43 have all the DISCARD requests, and then the WRITE requests and then the FLUSH
46 WRITE block 1, DISCARD block 1, FLUSH
48 If we logged DISCARD when it completed, the replay would look like this:
50 DISCARD 1, WRITE 1, FLUSH
/linux/tools/perf/arch/mips/entry/syscalls/
H A Dmksyscalltbl
/linux/tools/perf/arch/s390/entry/syscalls/
H A Dmksyscalltbl
/linux/arch/parisc/kernel/vdso64/
H A Dvdso64.lds.S83 /DISCARD/ : { *(.note.GNU-stack) }
84 /DISCARD/ : { *(.data .data.* .gnu.linkonce.d.* .sdata*) }
85 /DISCARD/ : { *(.bss .sbss .dynbss .dynsbss) }
/linux/arch/parisc/kernel/vdso32/
H A Dvdso32.lds.S85 /DISCARD/ : { *(.note.GNU-stack) }
86 /DISCARD/ : { *(.data .data.* .gnu.linkonce.d.* .sdata*) }
87 /DISCARD/ : { *(.bss .sbss .dynbss .dynsbss) }
/linux/fs/exfat/
H A Dsuper.c160 if (opts->discard) in exfat_show_options()
161 seq_puts(m, ",discard"); in exfat_show_options()
198 if (opts->discard) in exfat_force_shutdown()
199 opts->discard = 0; in exfat_force_shutdown()
275 fsparam_flag("discard", Opt_discard),
331 opts->discard = 1; in exfat_parse_param()
665 if (opts->discard && !bdev_max_discard_sectors(sb->s_bdev)) { in exfat_fill_super()
666 exfat_warn(sb, "mounting with \"discard\" option, but the device does not support discard"); in exfat_fill_super()
667 opts->discard = 0; in exfat_fill_super()

12345678910>>...35