| /linux/drivers/md/dm-vdo/ |
| H A D | repair.c | 172 static struct numbered_block_mapping *sort_next_heap_element(struct repair_completion *repair) in sort_next_heap_element() argument 174 struct replay_heap *heap = &repair->replay_heap; in sort_next_heap_element() 184 last = &repair->entries[--heap->nr]; in sort_next_heap_element() 203 static void prepare_repair_completion(struct repair_completion *repair, in prepare_repair_completion() argument 206 struct vdo_completion *completion = &repair->completion; in prepare_repair_completion() 218 static void launch_repair_completion(struct repair_completion *repair, in launch_repair_completion() argument 221 prepare_repair_completion(repair, callback, zone_type); in launch_repair_completion() 222 vdo_launch_completion(&repair->completion); in launch_repair_completion() 225 static void uninitialize_vios(struct repair_completion *repair) in uninitialize_vios() argument 227 while (repair->vio_count > 0) in uninitialize_vios() [all …]
|
| H A D | Makefile | 33 repair.o \
|
| /linux/Documentation/edac/ |
| H A D | memory_repair.rst | 20 Some memory devices support repair operations to address issues in their 28 device to perform repair operation on its media. It is a memory self-healing 36 - hard PPR, for a permanent row repair, and 37 - soft PPR, for a temporary row repair. 39 Soft PPR is much faster than hard PPR, but the repair is lost after a power 43 processed during a repair operation. In such case, the repair operation should 53 Memory sparing is a repair function that replaces a portion of memory with 82 Use cases of generic memory repair features control 87 repair control that is exposed to userspace and used by administrators, 91 host of the need for a repair maintenance operation by using an event [all …]
|
| H A D | scrub.rst | 42 statistics that are later used to decide whether to use memory repair
|
| /linux/fs/xfs/scrub/ |
| H A D | scrub.c | 283 .repair = xrep_probe, 289 .repair = xrep_superblock, 295 .repair = xrep_agf, 301 .repair = xrep_agfl, 307 .repair = xrep_agi, 313 .repair = xrep_allocbt, 320 .repair = xrep_allocbt, 327 .repair = xrep_iallocbt, 335 .repair = xrep_iallocbt, 343 .repair = xrep_rmapbt, [all …]
|
| H A D | repair.c | 75 ASSERT(sc->ops->repair); in xrep_attempt() 78 error = sc->ops->repair(sc); in xrep_attempt() 1149 error = sub->sc.ops->repair(&sub->sc); in xrep_metadata_inode_subtype()
|
| H A D | scrub.h | 88 int (*repair)(struct xfs_scrub *); member
|
| /linux/drivers/cxl/ |
| H A D | Kconfig | 172 The CXL EDAC memory repair control is optional and allows host 173 to control the memory repair features (e.g. sparing, PPR) 176 When enabled, the memory repair feature requires an additional 181 repair control attributes as described by 182 Documentation/ABI/testing/sysfs-edac-memory-repair. 185 of a memory repair feature established by the platform/device.
|
| /linux/drivers/ras/ |
| H A D | Kconfig | 13 enhanced by features that help to avoid, detect and repair hardware 21 which a system can be repaired or maintained; if the time to repair
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | sockmap_basic.c | 33 int s, repair, err; in connected_socket_v4() local 39 repair = TCP_REPAIR_ON; in connected_socket_v4() 40 err = setsockopt(s, SOL_TCP, TCP_REPAIR, &repair, sizeof(repair)); in connected_socket_v4() 48 repair = TCP_REPAIR_OFF_NO_WP; in connected_socket_v4() 49 err = setsockopt(s, SOL_TCP, TCP_REPAIR, &repair, sizeof(repair)); in connected_socket_v4()
|
| /linux/drivers/edac/ |
| H A D | mem_repair.c | 155 MR_DO_OP(repair, do_repair) 307 [MEM_DO_REPAIR] = __ATTR_WO(repair)
|
| /linux/tools/testing/selftests/net/tcp_ao/ |
| H A D | Makefile | 35 LIBSRC += proc.c repair.c setup.c sock.c utils.c
|
| /linux/Documentation/filesystems/ |
| H A D | btrfs.rst | 8 features while focusing on fault tolerance, repair and easy administration.
|
| H A D | zonefs.rst | 279 | repair | read-only | as is yes no yes no | 301 * The repair mount option triggers only the minimal set of I/O error recovery 323 * repair
|
| H A D | affs.rst | 191 restore or repair your RDB. So please do make a backup copy of it
|
| /linux/net/ipv4/ |
| H A D | tcp.c | 1141 !tp->repair) { in tcp_sendmsg_locked() 1164 if (unlikely(tp->repair)) { in tcp_sendmsg_locked() 1234 if (tp->repair) in tcp_sendmsg_locked() 1348 if (skb->len < size_goal || (flags & MSG_OOB) || unlikely(tp->repair)) in tcp_sendmsg_locked() 2665 if (unlikely(tp->repair)) { in tcp_recvmsg_locked() 3166 if (unlikely(tcp_sk(sk)->repair)) { in __tcp_close() 3364 } else if (unlikely(tp->repair)) { in tcp_disconnect() 3506 if (!tp->repair) in tcp_repair_set_window() 3974 tp->repair = 1; in do_tcp_setsockopt() 3978 tp->repair in do_tcp_setsockopt() [all...] |
| H A D | tcp_output.c | 2937 if (unlikely(tp->repair) && tp->repair_queue == TCP_SEND_QUEUE) { in tcp_write_xmit() 2943 goto repair; /* Skip network transmission */ in tcp_write_xmit() 3005 repair: in tcp_write_xmit() 4128 if (likely(!tp->repair)) in tcp_connect_init() 4317 if (unlikely(tp->repair)) { in tcp_connect()
|
| H A D | tcp_ao.c | 2390 if (!tp->repair) in tcp_ao_set_repair() 2423 if (!tp->repair) in tcp_ao_get_repair()
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | thin-provisioning.rst | 144 until the pool is taken offline and repair is performed to 1) fix any 145 potential inconsistencies and 2) clear the flag that imposes repair. 148 is flagged as needing repair, the pool's data and metadata devices 149 cannot be resized until repair is performed. It should also be noted 154 (e.g. fsck) be performed on those layers when repair of the pool is
|
| H A D | dm-raid.rst | 287 'sync_action' is "check" or "repair", then the process 309 repair 340 "repair" Initiate a repair of the array.
|
| /linux/fs/xfs/ |
| H A D | Makefile | 236 repair.o \
|
| H A D | Kconfig | 180 bool "XFS online metadata repair support" 185 If you say Y here you will be able to repair metadata on a
|
| /linux/fs/btrfs/ |
| H A D | Kconfig | 26 features focused on fault tolerance, repair and easy administration.
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-self-describing-metadata.rst | 77 metadata object at runtime, during forensic analysis or repair. 353 repair will probably complain about it - but it needs to be fixed.
|
| /linux/Documentation/driver-api/mtd/ |
| H A D | nand_ecc.rst | 736 introduced by this is about a factor 2 on my system when a repair had to 737 be done, and 1% or so if no repair had to be done.
|