ramdisk | RAM disk FUSE implementation in Go | File Utils library

As of 24 March 2022, Lambda supports a configurable ephemeral storage up to 10 GB of space.

Reference: https://aws.amazon.com/blogs/aws/aws-lambda-now-supports-up-to-10-gb-ephemeral-storage/

Hi the Redmi 8A has the same SoC but it has 64 bit kernel and OS... Some guys successfully ported 8A kernel to 7A of course not without problems.. In your case you may be able to combine 8A images with 7A... Hope this information helps you.

The LineageOS wiki has instructions on exporting the compiled emulator images and running them independently in an Android Virtual Device.

They should still work for pure AOSP as well.

Essentially, you can run mka sdk_addon to build a .zip file that contains all the necessary images for running the build in an emulator.

You don't need a loop; why can't you just use cp $^ $(PRODUCT_OUT)/boot ? However, the for loop DOES work. If you go look in the directory after the failure, don't you see the files you copied there? If something is failing you'll have to look for some other problem.

I will point out that unless you're setting oneshell in your makefile, this can't work:

memmap work by mapping pages in virtual memory (typically to physical memory pages or storage device ones like in your case). On most platforms, the size of pages is at least 4 KiB. As a result, any write in a page may cause the whole page to be updated.

SSDs and more generally flash memory works using block too, but they often use bigger chunks. Indeed, flash memory use cells with a very limited number of writes (eg. 1000). When cells are too much overwritten, they get unstable and may not be able to be read/written correctly. As a result, flash storage devices avoid any direct write access to cells and move written data blocks at a new location to save cells while being relatively fast. Once written, blocks cannot be mutated: a new block needs to be allocated and written to replace the old one. Thus, writing only few bytes randomly on a flash storage device cause it to allocate a lot of new blocks and copy a lot of (unchanged) data chunks. This also significantly impact the life of the target storage device. This can explain why SMART informations report such a high amount of IO writes.

Note that HDD do not have this issue but random writes are very slow compared to SSD (due to the time to move the heads). Alternative non-volatile RAM like ferroelectric RAM or magneto-resistive RAM can solve this issue correctly. Unfortunately, such RAMs are relatively experimental currently.

A possible fix is to store the modified data block in RAM, sort the block by location and write all of them at once. If the dataset is huge and the writes are very spread uniformly, then there is no solution on current mainstream hardware.

ByteBuffersDirectory is the replacement for RAMDirectory.

The chart below makes it crystal clear why RAMDiretory was depreciated and then removed. BBDIR is ByteBuffersDirectory and RAMDIR is RAMDirectory.

Chart by Dawid Weiss. Source: LUCENE-8438 and shown under Apache 2.0 License. .

So it turns out there is a short somewhere between the RX pin and the +3.3V pin which is not allowing me to send anything to the board. Thank you to those who have commented.

Your kernel command line says "console=tty0", which means "please send console to the first virtual terminal", ie to the graphics device. But there is no graphics device in the machine you're running (you say "-nographic" on your QEMU command line and the kernel says "Console: colour dummy device 80x25"). So what happens is that you see the initial bootup messages via the "uart8250" earlycon (ie the serial port), but as soon as the kernel gets to a point where it can honour your command line request, it enables tty0 (which goes nowhere) and disables uart8250 (so you see no further output).

You need to tell the kernel to send the console output to the serial port if that's where you'd like to see it appear, which for the malta board I think you can do by using "console=ttyS0" instead. Alternatively, you can drop '-nographic', make sure your kernel has the driver for the VGA card built in, and leave "console=tty0" and you'll see the console on the virtual console on the graphical window.

If you look at the README for the website you downloaded your image files from you'll see that it does indeed suggest using "console=ttyS0".

The problem was kernel had no drivers to SATA AHCI. The solution was to add a driver to configuration and rebuild kernel.