RME Audio DIGI32/8 Specifications download pdf (Page 14)

The `ramdisk_blocksize=' Argument

This can be tuned for better memory management behaviour. Quoting from the ramdisk driver rd.c:

It would be very desirable to have a soft−blocksize (that in the case of the ramdisk driver is also the

hardblocksize ;) of PAGE_SIZE because doing that we'll achieve a far better MM footprint. Using a

rd_blocksize of BLOCK_SIZE in the worst case we'll make PAGE_SIZE/BLOCK_SIZE buffer−pages

unfreeable. With a rd_blocksize of PAGE_SIZE instead we are sure that only 1 page will be protected.

Depending on the size of the ramdisk you may want to change the ramdisk blocksize to achieve a better or

worse MM behaviour. The default is still BLOCK_SIZE (needed by rd_load_image that supposes the

filesystem in the image uses a BLOCK_SIZE blocksize)

The `ramdisk=' Argument (obsolete)

(NOTE: This argument is obsolete, and should not be used except on kernels v1.3.47 and older. The

commands that should be used for the ramdisk device are documented above. Newer kernels may accept this

as an alias for ramdisk_size.)

This specifies the size in kB of the RAM disk device. For example, if one wished to have a root filesystem on

a 1.44MB floppy loaded into the RAM disk device, they would use:

ramdisk=1440

This is one of the few kernel boot arguments that has its default stored in the kernel image, and which can thus

be altered with the rdev utility.

The `noinitrd' (initial RAM disk) Argument

The v2.x and newer kernels have a feature where the root filesystem can be initially a RAM disk, and the

kernel executes /linuxrc on that RAM image. This feature is typically used to allow loading of modules

needed to mount the real root filesystem (e.g. load the SCSI driver modules stored in the RAM disk image,

and then mount the real root filesystem on a SCSI disk.)

The actual `noinitrd' argument determines what happens to the initrd data after the kernel has booted. When

specified, instead of converting it to a RAM disk, it is accessible via /dev/initrd, which can be read once

before the RAM is released back to the system. For full details on using the initial RAM disk, please consult

linux/Documentation/initrd.txt. In addition, the most recent versions of LILO and LOADLIN

should have additional useful information.

3.3 Boot Arguments Related to Memory Handling

The following arguments alter how Linux detects or handles the physical and virtual memory of your system.

The `cachesize=' Argument

Override level 2 CPU cache size detection (in kB). Sometimes CPU hardware bugs make them report the

cache size incorrectly. The kernel will attempt work arounds to fix known problems, but for some CPUs it is

not possible to determine what the correct size should be. This option provides an override for these

situations.

The Linux BootPrompt−HowTo

The `ramdisk_blocksize=' Argument 10

1 2 ... 9 10 11 12 13 14 15 16 17 18 19 ... 34 35

No comments

RME Audio DIGI32/8 Specifications Page 14