| /linux/arch/arc/kernel/ |
| H A D | vmlinux.lds.S | 119 /DISCARD/ : { *(.eh_frame) }
136 /DISCARD/ : { *(.debug_frame) }
137 /DISCARD/ : { *(.debug_aranges) }
138 /DISCARD/ : { *(.debug_pubnames) }
139 /DISCARD/ : { *(.debug_info) }
140 /DISCARD/ : { *(.debug_abbrev) }
141 /DISCARD/ : { *(.debug_line) }
142 /DISCARD/ : { *(.debug_str) }
143 /DISCARD/ : { *(.debug_loc) }
144 /DISCARD/ : { *(.debug_macinfo) }
[all …]
|
| /linux/include/xen/interface/io/ |
| H A D | blkif.h | 111 * 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 D | xfs_discard.c | 38 * 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 …]
|
| H A D | xfs_extent_busy.h | 26 #define XFS_EXTENT_BUSY_DISCARDED 0x01 /* undergoing a discard op. */
27 #define XFS_EXTENT_BUSY_SKIP_DISCARD 0x02 /* do not discard */
32 * to discard completion.
|
| /linux/Documentation/block/ |
| H A D | stat.rst | 40 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 D | jfs.rst | 52 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/tools/perf/tests/shell/ |
| H A D | test_arm_spe.sh | 111 echo "SPE discard mode"
114 if [ -e "$f/format/discard" ]; then
121 arm_spe_report "SPE discard mode not present" 2
127 # runs on an instance with discard mode otherwise we're not testing
129 perf record -o ${perfdata} -e arm_spe/discard/ -N -B --no-bpf-event \
133 arm_spe_report "SPE discard mode found unexpected data" 1
135 arm_spe_report "SPE discard mode" 0
|
| /linux/drivers/block/drbd/ |
| H A D | drbd_protocol.h | 60 /* 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 D | virtio_blk.h | 41 #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 D | interrupt.c | 60 * 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/include/linux/ |
| H A D | annotate.h | 17 __stringify(__ASM_ANNOTATE(.discard.annotate_insn, label, type))
21 __stringify(__ASM_ANNOTATE(.discard.annotate_insn, 911b, type))
25 __stringify(__ASM_ANNOTATE(.discard.annotate_data, 912b, type))
31 __ASM_ANNOTATE(.discard.annotate_insn, .Lhere_\@, \type)
36 __ASM_ANNOTATE(.discard.annotate_data, .Lhere_\@, \type)
|
| /linux/net/wireless/ |
| H A D | wext-proc.c | 61 stats->discard.nwid, stats->discard.code, in wireless_seq_printf_stats()
62 stats->discard.fragment, stats->discard.retries, in wireless_seq_printf_stats()
63 stats->discard.misc, stats->miss.beacon); in wireless_seq_printf_stats()
|
| /linux/Documentation/bpf/ |
| H A D | ringbuf.rst | 93 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/dccp/ |
| H A D | input.c | |
| /linux/drivers/firmware/efi/libstub/ |
| H A D | zboot.lds | 52 /DISCARD/ : {
53 *(.discard .discard.*)
|
| /linux/drivers/block/xen-blkback/ |
| H A D | blkback.c | 976 preq.sector_number = req->u.discard.sector_number; in dispatch_discard_io()
977 preq.nr_sects = req->u.discard.nr_sectors; in dispatch_discard_io()
981 pr_warn("access denied: DISCARD [%llu->%llu] on dev=%04x\n", in dispatch_discard_io()
989 (req->u.discard.flag & BLKIF_DISCARD_SECURE)) in dispatch_discard_io()
991 req->u.discard.sector_number, in dispatch_discard_io()
992 req->u.discard.nr_sectors, GFP_KERNEL); in dispatch_discard_io()
994 err = blkdev_issue_discard(bdev, req->u.discard.sector_number, in dispatch_discard_io()
995 req->u.discard.nr_sectors, GFP_KERNEL); in dispatch_discard_io()
999 pr_debug("discard op failed, not supported\n"); in dispatch_discard_io()
1004 make_response(ring, req->u.discard.id, req->operation, status); in dispatch_discard_io()
[all …]
|
| /linux/arch/mips/include/asm/ |
| H A D | yamon-dt.h | 16 * @discard: Length of additional memory to discard after the region.
21 phys_addr_t discard; member
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-arm-spe.txt | 25 3. Optionally discard the record based on a filter
44 Optionally discard the record based on a filter
47 Based on programmable criteria, choose whether to keep the record or discard it. If the record is
151 discard=1 - enable SPE PMU events but don't collect sample data - see 'Discard mode' (PMBLIMITR.FM = DISCARD)
311 Discard mode
315 collecting sample data if discard mode is supported (optional from Armv8.6).
319 perf record -e arm_spe/discard/ -a -N -B --no-bpf-event -o - > /dev/null &
|
| /linux/include/uapi/asm-generic/ |
| H A D | termbits-common.h | 62 #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 D | module.lds.S | 10 /DISCARD/ : {
11 *(.discard)
12 *(.discard.*)
|
| /linux/arch/arm64/kernel/vdso/ |
| H A D | vdso.lds.S | 36 * Discard .note.gnu.property sections which are unused and have
39 /DISCARD/ : {
77 /DISCARD/ : {
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | log-writes.rst | 43 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/net/ipv6/ |
| H A D | ip6_input.c | 422 goto discard; in ip6_protocol_deliver_rcu()
439 goto discard; in ip6_protocol_deliver_rcu()
458 goto discard; in ip6_protocol_deliver_rcu()
468 goto discard; in ip6_protocol_deliver_rcu()
474 goto discard; in ip6_protocol_deliver_rcu()
493 goto discard; in ip6_protocol_deliver_rcu()
519 discard: in ip6_protocol_deliver_rcu()
638 /* discard */ in ip6_mc_input()
|
| /linux/arch/parisc/kernel/vdso64/ |
| H A D | vdso64.lds.S | 83 /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 D | vdso32.lds.S | 85 /DISCARD/ : { *(.note.GNU-stack) }
86 /DISCARD/ : { *(.data .data.* .gnu.linkonce.d.* .sdata*) }
87 /DISCARD/ : { *(.bss .sbss .dynbss .dynsbss) }
|