Podcast about the 2012 LinkedIn data breach – who,how,when
darknetdiaries.com2 pointsby tkinom0 comments
System performance scales well with latest SSD HW.
As compare to cloud base approach that is limited by network/cloud speed.
One can store logs per day / week / year in separate db files as needed.
Backup of small db files for last few days/weeks are trivial with rsync.
Can be for old laptop (T420, etc with Intel GPU/Driver.)
Use FTRACE in kernel.
Setup ebpf trace for GPU acitivies.
Write some doc/blog/medium pages on the process and show off your works.
Understand, document and improve some opensource GPU API related utilities
Understand and document interaction between GPU/GUI App and OpenSource driver.
https://www.zdnet.com/article/hackerones-2020-top-10-public-bug-bounty-programs/
Use pre-allocated pools with array of indexes, free/allocation idx for alloc and free.
Con: Fixed pool size and fixed amount of memory can be allocated per pool.
Pro: constant cost operations per alloc/free via Atomic inc/dec of idx - no linklist tranversing ; Can be alloc in kernel space and free in user space (linux/QNX) and in multiple user processes when memory pools are in shmem; Run very will in SMP environment without any locks - all memory contentions were handled with atomic +/- alloc/free idx.
Same source code run in QNX, vxworks and linux (kernel and user space) at that time.