File manager

File manager - Edit - /home/newsbmcs.com/public_html/static/img/logo/block.tar

Back
Kconfig��0000644��00000016101�15027533702�0006052 0��ustar�00��# SPDX-License-Identifier: GPL-2.0 # # Block layer core configuration # menuconfig BLOCK bool "Enable the block layer" if EXPERT default y select SBITMAP select SRCU help Provide block layer support for the kernel. Disable this option to remove the block layer support from the kernel. This may be useful for embedded devices. If this option is disabled: - block device files will become unusable - some filesystems (such as ext3) will become unavailable. Also, SCSI character devices and USB storage will be disabled since they make use of various block layer definitions and facilities. Say Y here unless you know you really don't want to mount disks and suchlike. if BLOCK config BLOCK_LEGACY_AUTOLOAD bool "Legacy autoloading support" help Enable loading modules and creating block device instances based on accesses through their device special file. This is a historic Linux feature and makes no sense in a udev world where device files are created on demand. Say N here unless booting or other functionality broke without it, in which case you should also send a report to your distribution and linux-block@vger.kernel.org. config BLK_RQ_ALLOC_TIME bool config BLK_CGROUP_RWSTAT bool config BLK_DEV_BSG_COMMON tristate config BLK_DEV_BSGLIB bool "Block layer SG support v4 helper lib" select BLK_DEV_BSG_COMMON help Subsystems will normally enable this if needed. Users will not normally need to manually enable this. If unsure, say N. config BLK_DEV_INTEGRITY bool "Block layer data integrity support" help Some storage devices allow extra information to be stored/retrieved to help protect the data. The block layer data integrity option provides hooks which can be used by filesystems to ensure better data integrity. Say yes here if you have a storage device that provides the T10/SCSI Data Integrity Field or the T13/ATA External Path Protection. If in doubt, say N. config BLK_DEV_INTEGRITY_T10 tristate depends on BLK_DEV_INTEGRITY select CRC_T10DIF config BLK_DEV_ZONED bool "Zoned block device support" select MQ_IOSCHED_DEADLINE help Block layer zoned block device support. This option enables support for ZAC/ZBC/ZNS host-managed and host-aware zoned block devices. Say yes here if you have a ZAC, ZBC, or ZNS storage device. config BLK_DEV_THROTTLING bool "Block layer bio throttling support" depends on BLK_CGROUP=y select BLK_CGROUP_RWSTAT help Block layer bio throttling support. It can be used to limit the IO rate to a device. IO rate policies are per cgroup and one needs to mount and use blkio cgroup controller for creating cgroups and specifying per device IO rate policies. See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information. config BLK_DEV_THROTTLING_LOW bool "Block throttling .low limit interface support (EXPERIMENTAL)" depends on BLK_DEV_THROTTLING help Add .low limit interface for block throttling. The low limit is a best effort limit to prioritize cgroups. Depending on the setting, the limit can be used to protect cgroups in terms of bandwidth/iops and better utilize disk resource. Note, this is an experimental interface and could be changed someday. config BLK_WBT bool "Enable support for block device writeback throttling" help Enabling this option enables the block layer to throttle buffered background writeback from the VM, making it more smooth and having less impact on foreground operations. The throttling is done dynamically on an algorithm loosely based on CoDel, factoring in the realtime performance of the disk. config BLK_WBT_MQ bool "Enable writeback throttling by default" default y depends on BLK_WBT help Enable writeback throttling by default for request-based block devices. config BLK_CGROUP_IOLATENCY bool "Enable support for latency based cgroup IO protection" depends on BLK_CGROUP=y help Enabling this option enables the .latency interface for IO throttling. The IO controller will attempt to maintain average IO latencies below the configured latency target, throttling anybody with a higher latency target than the victimized group. Note, this is an experimental interface and could be changed someday. config BLK_CGROUP_FC_APPID bool "Enable support to track FC I/O Traffic across cgroup applications" depends on BLK_CGROUP && NVME_FC help Enabling this option enables the support to track FC I/O traffic across cgroup applications. It enables the Fabric and the storage targets to identify, monitor, and handle FC traffic based on VM tags by inserting application specific identification into the FC frame. config BLK_CGROUP_IOCOST bool "Enable support for cost model based cgroup IO controller" depends on BLK_CGROUP=y select BLK_RQ_IO_DATA_LEN select BLK_RQ_ALLOC_TIME help Enabling this option enables the .weight interface for cost model based proportional IO control. The IO controller distributes IO capacity between different groups based on their share of the overall weight distribution. config BLK_CGROUP_IOPRIO bool "Cgroup I/O controller for assigning an I/O priority class" depends on BLK_CGROUP help Enable the .prio interface for assigning an I/O priority class to requests. The I/O priority class affects the order in which an I/O scheduler and block devices process requests. Only some I/O schedulers and some block devices support I/O priorities. config BLK_DEBUG_FS bool "Block layer debugging information in debugfs" default y depends on DEBUG_FS help Include block layer debugging information in debugfs. This information is mostly useful for kernel developers, but it doesn't incur any cost at runtime. Unless you are building a kernel for a tiny system, you should say Y here. config BLK_DEBUG_FS_ZONED bool default BLK_DEBUG_FS && BLK_DEV_ZONED config BLK_SED_OPAL bool "Logic for interfacing with Opal enabled SEDs" help Builds Logic for interfacing with Opal enabled controllers. Enabling this option enables users to setup/unlock/lock Locking ranges for SED devices using the Opal protocol. config BLK_INLINE_ENCRYPTION bool "Enable inline encryption support in block layer" help Build the blk-crypto subsystem. Enabling this lets the block layer handle encryption, so users can take advantage of inline encryption hardware if present. config BLK_INLINE_ENCRYPTION_FALLBACK bool "Enable crypto API fallback for blk-crypto" depends on BLK_INLINE_ENCRYPTION select CRYPTO select CRYPTO_SKCIPHER help Enabling this lets the block layer handle inline encryption by falling back to the kernel crypto API when inline encryption hardware is not present. menu "Partition Types" source "block/partitions/Kconfig" endmenu endif # BLOCK config BLOCK_COMPAT bool depends on BLOCK && COMPAT default y config BLK_MQ_PCI bool depends on BLOCK && PCI default y config BLK_MQ_VIRTIO bool depends on BLOCK && VIRTIO default y config BLK_MQ_RDMA bool depends on BLOCK && INFINIBAND default y config BLK_PM def_bool BLOCK && PM # do not use in new code config BLOCK_HOLDER_DEPRECATED bool source "block/Kconfig.iosched" ��partitions/Kconfig��0000644��00000023115�15027533702�0010251 0��ustar�00��# SPDX-License-Identifier: GPL-2.0 # # Partition configuration # config PARTITION_ADVANCED bool "Advanced partition selection" help Say Y here if you would like to use hard disks under Linux which were partitioned under an operating system running on a different architecture than your Linux system. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about foreign partitioning schemes. If unsure, say N. config ACORN_PARTITION bool "Acorn partition support" if PARTITION_ADVANCED default y if ARCH_ACORN help Support hard disks partitioned under Acorn operating systems. config ACORN_PARTITION_CUMANA bool "Cumana partition support" if PARTITION_ADVANCED default y if ARCH_ACORN depends on ACORN_PARTITION help Say Y here if you would like to use hard disks under Linux which were partitioned using the Cumana interface on Acorn machines. config ACORN_PARTITION_EESOX bool "EESOX partition support" if PARTITION_ADVANCED default y if ARCH_ACORN depends on ACORN_PARTITION config ACORN_PARTITION_ICS bool "ICS partition support" if PARTITION_ADVANCED default y if ARCH_ACORN depends on ACORN_PARTITION help Say Y here if you would like to use hard disks under Linux which were partitioned using the ICS interface on Acorn machines. config ACORN_PARTITION_ADFS bool "Native filecore partition support" if PARTITION_ADVANCED default y if ARCH_ACORN depends on ACORN_PARTITION help The Acorn Disc Filing System is the standard file system of the RiscOS operating system which runs on Acorn's ARM-based Risc PC systems and the Acorn Archimedes range of machines. If you say `Y' here, Linux will support disk partitions created under ADFS. config ACORN_PARTITION_POWERTEC bool "PowerTec partition support" if PARTITION_ADVANCED default y if ARCH_ACORN depends on ACORN_PARTITION help Support reading partition tables created on Acorn machines using the PowerTec SCSI drive. config ACORN_PARTITION_RISCIX bool "RISCiX partition support" if PARTITION_ADVANCED default y if ARCH_ACORN depends on ACORN_PARTITION help Once upon a time, there was a native Unix port for the Acorn series of machines called RISCiX. If you say 'Y' here, Linux will be able to read disks partitioned under RISCiX. config AIX_PARTITION bool "AIX basic partition table support" if PARTITION_ADVANCED help Say Y here if you would like to be able to read the hard disk partition table format used by IBM or Motorola PowerPC machines running AIX. AIX actually uses a Logical Volume Manager, where "logical volumes" can be spread across one or multiple disks, but this driver works only for the simple case of partitions which are contiguous. Otherwise, say N. config OSF_PARTITION bool "Alpha OSF partition support" if PARTITION_ADVANCED default y if ALPHA help Say Y here if you would like to use hard disks under Linux which were partitioned on an Alpha machine. config AMIGA_PARTITION bool "Amiga partition table support" if PARTITION_ADVANCED default y if (AMIGA \|\| AFFS_FS=y) help Say Y here if you would like to use hard disks under Linux which were partitioned under AmigaOS. config ATARI_PARTITION bool "Atari partition table support" if PARTITION_ADVANCED default y if ATARI help Say Y here if you would like to use hard disks under Linux which were partitioned under the Atari OS. config IBM_PARTITION bool "IBM disk label and partition support" depends on PARTITION_ADVANCED && S390 help Say Y here if you would like to be able to read the hard disk partition table format used by IBM DASD disks operating under CMS. Otherwise, say N. config MAC_PARTITION bool "Macintosh partition map support" if PARTITION_ADVANCED default y if (MAC \|\| PPC_PMAC) help Say Y here if you would like to use hard disks under Linux which were partitioned on a Macintosh. config MSDOS_PARTITION bool "PC BIOS (MSDOS partition tables) support" if PARTITION_ADVANCED default y help Say Y here. config BSD_DISKLABEL bool "BSD disklabel (FreeBSD partition tables) support" depends on PARTITION_ADVANCED && MSDOS_PARTITION help FreeBSD uses its own hard disk partition scheme on your PC. It requires only one entry in the primary partition table of your disk and manages it similarly to DOS extended partitions, putting in its first sector a new partition table in BSD disklabel format. Saying Y here allows you to read these disklabels and further mount FreeBSD partitions from within Linux if you have also said Y to "UFS file system support", above. If you don't know what all this is about, say N. config MINIX_SUBPARTITION bool "Minix subpartition support" depends on PARTITION_ADVANCED && MSDOS_PARTITION help Minix 2.0.0/2.0.2 subpartition table support for Linux. Say Y here if you want to mount and use Minix 2.0.0/2.0.2 subpartitions. config SOLARIS_X86_PARTITION bool "Solaris (x86) partition table support" depends on PARTITION_ADVANCED && MSDOS_PARTITION help Like most systems, Solaris x86 uses its own hard disk partition table format, incompatible with all others. Saying Y here allows you to read these partition tables and further mount Solaris x86 partitions from within Linux if you have also said Y to "UFS file system support", above. config UNIXWARE_DISKLABEL bool "Unixware slices support" depends on PARTITION_ADVANCED && MSDOS_PARTITION help Like some systems, UnixWare uses its own slice table inside a partition (VTOC - Virtual Table of Contents). Its format is incompatible with all other OSes. Saying Y here allows you to read VTOC and further mount UnixWare partitions read-only from within Linux if you have also said Y to "UFS file system support" or "System V and Coherent file system support", above. This is mainly used to carry data from a UnixWare box to your Linux box via a removable medium like magneto-optical, ZIP or removable IDE drives. Note, however, that a good portable way to transport files and directories between unixes (and even other operating systems) is given by the tar program ("man tar" or preferably "info tar"). If you don't know what all this is about, say N. config LDM_PARTITION bool "Windows Logical Disk Manager (Dynamic Disk) support" depends on PARTITION_ADVANCED help Say Y here if you would like to use hard disks under Linux which were partitioned using Windows 2000's/XP's or Vista's Logical Disk Manager. They are also known as "Dynamic Disks". Note this driver only supports Dynamic Disks with a protective MBR label, i.e. DOS partition table. It does not support GPT labelled Dynamic Disks yet as can be created with Vista. Windows 2000 introduced the concept of Dynamic Disks to get around the limitations of the PC's partitioning scheme. The Logical Disk Manager allows the user to repartition a disk and create spanned, mirrored, striped or RAID volumes, all without the need for rebooting. Normal partitions are now called Basic Disks under Windows 2000, XP, and Vista. For a fuller description read <file:Documentation/admin-guide/ldm.rst>. If unsure, say N. config LDM_DEBUG bool "Windows LDM extra logging" depends on LDM_PARTITION help Say Y here if you would like LDM to log verbosely. This could be helpful if the driver doesn't work as expected and you'd like to report a bug. If unsure, say N. config SGI_PARTITION bool "SGI partition support" if PARTITION_ADVANCED default y if DEFAULT_SGI_PARTITION help Say Y here if you would like to be able to read the hard disk partition table format used by SGI machines. config ULTRIX_PARTITION bool "Ultrix partition table support" if PARTITION_ADVANCED default y if MACH_DECSTATION help Say Y here if you would like to be able to read the hard disk partition table format used by DEC (now Compaq) Ultrix machines. Otherwise, say N. config SUN_PARTITION bool "Sun partition tables support" if PARTITION_ADVANCED default y if (SPARC \|\| SUN3 \|\| SUN3X) help Like most systems, SunOS uses its own hard disk partition table format, incompatible with all others. Saying Y here allows you to read these partition tables and further mount SunOS partitions from within Linux if you have also said Y to "UFS file system support", above. This is mainly used to carry data from a SPARC under SunOS to your Linux box via a removable medium like magneto-optical or ZIP drives; note however that a good portable way to transport files and directories between unixes (and even other operating systems) is given by the tar program ("man tar" or preferably "info tar"). If you don't know what all this is about, say N. config KARMA_PARTITION bool "Karma Partition support" depends on PARTITION_ADVANCED help Say Y here if you would like to mount the Rio Karma MP3 player, as it uses a proprietary partition table. config EFI_PARTITION bool "EFI GUID Partition support" if PARTITION_ADVANCED default y select CRC32 help Say Y here if you would like to use hard disks under Linux which were partitioned using EFI GPT. config SYSV68_PARTITION bool "SYSV68 partition table support" if PARTITION_ADVANCED default y if VME help Say Y here if you would like to be able to read the hard disk partition table format used by Motorola Delta machines (using sysv68). Otherwise, say N. config CMDLINE_PARTITION bool "Command line partition support" if PARTITION_ADVANCED help Say Y here if you want to read the partition table from bootargs. The format for the command line is just like mtdparts. ��partitions/Makefile��0000644��00000001337�15027533702�0010410 0��ustar�00��# SPDX-License-Identifier: GPL-2.0 # # Makefile for the linux kernel. # obj-$(CONFIG_BLOCK) += core.o obj-$(CONFIG_ACORN_PARTITION) += acorn.o obj-$(CONFIG_AMIGA_PARTITION) += amiga.o obj-$(CONFIG_ATARI_PARTITION) += atari.o obj-$(CONFIG_AIX_PARTITION) += aix.o obj-$(CONFIG_CMDLINE_PARTITION) += cmdline.o obj-$(CONFIG_MAC_PARTITION) += mac.o obj-$(CONFIG_LDM_PARTITION) += ldm.o obj-$(CONFIG_MSDOS_PARTITION) += msdos.o obj-$(CONFIG_OSF_PARTITION) += osf.o obj-$(CONFIG_SGI_PARTITION) += sgi.o obj-$(CONFIG_SUN_PARTITION) += sun.o obj-$(CONFIG_ULTRIX_PARTITION) += ultrix.o obj-$(CONFIG_IBM_PARTITION) += ibm.o obj-$(CONFIG_EFI_PARTITION) += efi.o obj-$(CONFIG_KARMA_PARTITION) += karma.o obj-$(CONFIG_SYSV68_PARTITION) += sysv68.o ��Makefile��0000644��00000003267�15027533702�0006220 0��ustar�00��# SPDX-License-Identifier: GPL-2.0 # # Makefile for the kernel block layer # obj-y := bdev.o fops.o bio.o elevator.o blk-core.o blk-sysfs.o \ blk-flush.o blk-settings.o blk-ioc.o blk-map.o \ blk-exec.o blk-merge.o blk-timeout.o \ blk-lib.o blk-mq.o blk-mq-tag.o blk-stat.o \ blk-mq-sysfs.o blk-mq-cpumap.o blk-mq-sched.o ioctl.o \ genhd.o ioprio.o badblocks.o partitions/ blk-rq-qos.o \ disk-events.o obj-$(CONFIG_BOUNCE) += bounce.o obj-$(CONFIG_BLK_DEV_BSG_COMMON) += bsg.o obj-$(CONFIG_BLK_DEV_BSGLIB) += bsg-lib.o obj-$(CONFIG_BLK_CGROUP) += blk-cgroup.o obj-$(CONFIG_BLK_CGROUP_RWSTAT) += blk-cgroup-rwstat.o obj-$(CONFIG_BLK_DEV_THROTTLING) += blk-throttle.o obj-$(CONFIG_BLK_CGROUP_IOPRIO) += blk-ioprio.o obj-$(CONFIG_BLK_CGROUP_IOLATENCY) += blk-iolatency.o obj-$(CONFIG_BLK_CGROUP_IOCOST) += blk-iocost.o obj-$(CONFIG_MQ_IOSCHED_DEADLINE) += mq-deadline.o obj-$(CONFIG_MQ_IOSCHED_KYBER) += kyber-iosched.o bfq-y := bfq-iosched.o bfq-wf2q.o bfq-cgroup.o obj-$(CONFIG_IOSCHED_BFQ) += bfq.o obj-$(CONFIG_BLK_DEV_INTEGRITY) += bio-integrity.o blk-integrity.o obj-$(CONFIG_BLK_DEV_INTEGRITY_T10) += t10-pi.o obj-$(CONFIG_BLK_MQ_PCI) += blk-mq-pci.o obj-$(CONFIG_BLK_MQ_VIRTIO) += blk-mq-virtio.o obj-$(CONFIG_BLK_MQ_RDMA) += blk-mq-rdma.o obj-$(CONFIG_BLK_DEV_ZONED) += blk-zoned.o obj-$(CONFIG_BLK_WBT) += blk-wbt.o obj-$(CONFIG_BLK_DEBUG_FS) += blk-mq-debugfs.o obj-$(CONFIG_BLK_DEBUG_FS_ZONED)+= blk-mq-debugfs-zoned.o obj-$(CONFIG_BLK_SED_OPAL) += sed-opal.o obj-$(CONFIG_BLK_PM) += blk-pm.o obj-$(CONFIG_BLK_INLINE_ENCRYPTION) += keyslot-manager.o blk-crypto.o obj-$(CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK) += blk-crypto-fallback.o obj-$(CONFIG_BLOCK_HOLDER_DEPRECATED) += holder.o ��Kconfig.iosched��0000644��00000002531�15027533702�0007471 0��ustar�00��# SPDX-License-Identifier: GPL-2.0 if BLOCK menu "IO Schedulers" config MQ_IOSCHED_DEADLINE tristate "MQ deadline I/O scheduler" default y help MQ version of the deadline IO scheduler. config MQ_IOSCHED_KYBER tristate "Kyber I/O scheduler" default y help The Kyber I/O scheduler is a low-overhead scheduler suitable for multiqueue and other fast devices. Given target latencies for reads and synchronous writes, it will self-tune queue depths to achieve that goal. config IOSCHED_BFQ tristate "BFQ I/O scheduler" help BFQ I/O scheduler for BLK-MQ. BFQ distributes the bandwidth of of the device among all processes according to their weights, regardless of the device parameters and with any workload. It also guarantees a low latency to interactive and soft real-time applications. Details in Documentation/block/bfq-iosched.rst config BFQ_GROUP_IOSCHED bool "BFQ hierarchical scheduling support" depends on IOSCHED_BFQ && BLK_CGROUP select BLK_CGROUP_RWSTAT help Enable hierarchical scheduling in BFQ, using the blkio (cgroups-v1) or io (cgroups-v2) controller. config BFQ_CGROUP_DEBUG bool "BFQ IO controller debugging" depends on BFQ_GROUP_IOSCHED help Enable some debugging help. Currently it exports additional stat files in a cgroup which can be useful for debugging. endmenu endif ��

| ver. 1.4 | Github | . | PHP 8.2.28 | Generation time: 0.02 | proxy | phpinfo | Settings