Skip to main content

Posts

Showing posts with the label limit

FDisk: Fixing What GParted Can’t

After my foray into making bootable flash drives , I decided to put my flash drive back to its original state. It was going to take at least a little bit of effort since I know had multiple partitions on the drive which would need to be removed. I first went to my default disk utility, GParted. GParted allowed me to first unmount the partitions that Linux was auto-mounting as drives. I was then able to delete the partitions to make the drive completely unallocated space. That’s where I started to run into issues. I went to make the entire drive a single FAT32 partition, but GParted gave me the following .... Read More

be the kind of person

OpenVZ VSwap

New  RHEL6-based OpenVZ  kernel has a new memory management model, which supersedes  User beancounters . It is called  VSwap . Now you can set two primary parameters:  physpages  and  swappages , while all the other beancounters become secondary. physpages This parameter limits the physical memory (RAM) available to processes inside a container. The  barrier  is ignored, and the  limit  sets the limit. Currently the user memory and the page cache are accounted into  physpages . swappages This parameter limits the amount of swap space which can be used for processes inside a container. The  barrier  is ignored, and the  limit  sets the limit. The sum of physpages.limit and swappages.limit limits the maximum amount of allocated memory which can be used by a container. When physpages limit is reached, memory pages belonging to the container are pushed out to so called virtual swap ( vswap ). The d...