| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-edac-memory-repair | 7 pertains to the memory media repair features control, such as 10 device driver for the memory repair features. 13 device to perform a repair operation on its media. It is a memory 18 two types of PPR functions: hard PPR, for a permanent row repair, and 19 soft PPR, for a temporary row repair. Soft PPR may be much faster 20 than hard PPR, but the repair is lost with a power cycle. 22 The sysfs attributes nodes for a repair feature are only 30 physical address map. As such, the memory to repair must be 40 (RO) Memory repair type. For eg. post package repair, 43 - ppr - Post package repair. [all …]
|
| /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/drivers/cxl/ |
| H A D | Kconfig | 173 The CXL EDAC memory repair control is optional and allows host 174 to control the memory repair features (e.g. sparing, PPR) 177 When enabled, the memory repair feature requires an additional 182 repair control attributes as described by 183 Documentation/ABI/testing/sysfs-edac-memory-repair. 186 of a memory repair feature established by the platform/device.
|
| /linux/tools/testing/selftests/net/tcp_ao/ |
| H A D | Makefile | 35 LIBSRC += proc.c repair.c setup.c sock.c utils.c
|
| /linux/drivers/md/dm-vdo/ |
| H A D | Makefile | 33 repair.o \
|
| /linux/drivers/edac/ |
| H A D | mem_repair.c | 155 MR_DO_OP(repair, do_repair) 307 [MEM_DO_REPAIR] = __ATTR_WO(repair)
|
| /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/tools/testing/selftests/bpf/prog_tests/ |
| H A D | sockmap_basic.c | 43 int s, repair, err; in connected_socket_v4() local 49 repair = TCP_REPAIR_ON; in connected_socket_v4() 50 err = setsockopt(s, SOL_TCP, TCP_REPAIR, &repair, sizeof(repair)); in connected_socket_v4() 58 repair = TCP_REPAIR_OFF_NO_WP; in connected_socket_v4() 59 err = setsockopt(s, SOL_TCP, TCP_REPAIR, &repair, sizeof(repair)); in connected_socket_v4()
|
| /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
|
| /linux/fs/xfs/scrub/ |
| H A D | scrub.h | 88 int (*repair)(struct xfs_scrub *); member
|
| /linux/fs/btrfs/ |
| H A D | Kconfig | 24 features focused on fault tolerance, repair and easy administration.
|
| /linux/fs/xfs/ |
| 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/include/linux/ |
| H A D | tcp.h | 231 u8 repair : 1, member
|
| /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/net/ipv4/ |
| H A D | tcp_output.c | 2997 if (unlikely(tp->repair) && tp->repair_queue == TCP_SEND_QUEUE) { in tcp_write_xmit() 3003 goto repair; /* Skip network transmission */ in tcp_write_xmit() 3065 repair: in tcp_write_xmit() 4168 if (likely(!tp->repair)) in tcp_connect_init() 4362 if (unlikely(tp->repair)) { in tcp_connect()
|
| H A D | tcp_ipv4.c | 178 /* In case of repair and re-using TIME-WAIT sockets we still in tcp_twsk_unique() 180 * sequence numbers and time stamps set as part of the repair in tcp_twsk_unique() 184 * repair would accumulate a -1 on the repair assigned in tcp_twsk_unique() 189 if (likely(!tp->repair)) { in tcp_twsk_unique() 287 if (likely(!tp->repair)) in tcp_v4_connect() 325 if (likely(!tp->repair)) { in tcp_v4_connect()
|
| H A D | tcp_ao.c | 2379 if (!tp->repair) in tcp_ao_set_repair() 2412 if (!tp->repair) in tcp_ao_get_repair()
|
| /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.
|
| /linux/Documentation/power/ |
| H A D | freezing-of-tasks.rst | 125 usually making them almost impossible to repair). We therefore freeze
|
| /linux/Documentation/process/ |
| H A D | changes.rst | 267 and repair a JFS formatted partition.
|
| /linux/Documentation/ |
| H A D | Changes | 267 and repair a JFS formatted partition.
|
| /linux/Documentation/scsi/ |
| H A D | ChangeLog.ncr53c8xx | 390 Use SCRIPTS to repair the start queue on selection timeout.
|