Tiny Core Base > TCB Bugs

printf in /init, it has missing "f"

<< < (2/4) > >>

curaga:
Do you have GNU awk loaded? In my tests busybox awk doesn't do e6 rounding, it requires hundreds of millions before it starts to round.

In any case, that will affect very large memory systems, so pushed a fix.

nick65go:
no GNU awk explicit loaded by me. Maybe some extensions load it, but very improbable.
anyway, thanks for fix, i saw it at https://github.com/tinycorelinux/Core-scripts/commit/f92dbfe23a97ca757b2fc4987b726528d3b2ac72
may i, how about the logic/know-how for MEM div 3 for inode of tmpfs?

curaga:
I don't remember, sorry.

nick65go:
sorry i am not on linux to test it now, but

why
--- Code: --- inodes=`grep MemFree /proc/meminfo | awk '{printf("%d\n", $2/3)}'`
--- End code ---
why not just something like :
--- Code: ---inodes=`grep MemFree /proc/meminfo | printf "%d\n", $2/3
--- End code ---
anyway  i guess that is just mili-seconds diff in speed.

nick65go:
Looking over https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt , Updated: KOSAKI Motohiro, 16 Mar 2010 (so old!)
the string "nr_inodes" shows only 3 times.

1. "So 'mount -t tmpfs -o size=10G,nr_inodes=10k,mode=700 tmpfs /mytmpfs' will give you tmpfs instance on /mytmpfs which can allocate 10GB RAM/SWAP in 10240 inodes and it is only accessible by root" <--is Not very useful.

2. "nr_inodes: The maximum number of inodes for this instance. The default is half of the number of your physical RAM pages, or (on a machine with highmem) the number of lowmem RAM pages, whichever is the lower." <--so we need to specify something about inode (but not necesary 1/3 of RAM)

3. "if nr_inodes=0, inodes will not be limited.  It is generally unwise to mount with such options, since it allows any user with write access to use up all the memory on the machine; but enhances the scalability of that instance in a system with many cpus making intensive use of it." <-- like most modern forced UEFI_64 with shame-less multicore CPU (> 4+ cores).

But here is the thing, we use 90% of RAM, and we use zram for compressed_swap in memory. So no danger to exhaust all RAM inodes, I think.
So, if I am not wrong, nr_inode parameter for mount can be zero (aka missing)?

Navigation

[0] Message Index

[#] Next page

[*] Previous page