Editing Memory paging (section)

=====Swap files and partitions=====
From the end-user perspective, swap files in versions 2.6.x and later of the Linux kernel are virtually as fast as swap partitions; the limitation is that swap files should be contiguously allocated on their underlying file systems.  To increase performance of swap files, the kernel keeps a map of where they are placed on underlying devices and accesses them directly, thus bypassing the cache and avoiding filesystem overhead.<ref>{{cite web |url=https://lkml.org/lkml/2006/5/29/3 |title="Jesper Juhl": Re: How to send a break? - dump from frozen 64bit linux |publisher=LKML |date=2006-05-29 |access-date=2010-10-28 |url-status=live |archive-url=https://web.archive.org/web/20101124235412/http://lkml.org/lkml/2006/5/29/3 |archive-date=2010-11-24 }}</ref><ref>{{cite web |url=https://lkml.org/lkml/2005/7/7/326 |title=Andrew Morton: Re: Swap partition vs swap file |publisher=LKML |access-date=2010-10-28 |url-status=live |archive-url=https://web.archive.org/web/20101124235448/http://lkml.org/lkml/2005/7/7/326 |archive-date=2010-11-24 }}</ref> When residing on HDDs, which are rotational magnetic media devices, one benefit of using swap partitions is the ability to place them on contiguous HDD areas that provide higher data throughput or faster seek time. However, the administrative flexibility of swap files can outweigh certain advantages of swap partitions. For example, a swap file can be placed on any mounted file system, can be set to any desired size, and can be added or changed as needed. Swap partitions are not as flexible; they cannot be enlarged without using partitioning or [[Logical volume management|volume management]] tools, which introduce various complexities and potential downtimes.