<div dir="ltr"><div class="gmail_default" style="font-family:trebuchet ms,sans-serif;font-size:small"><span style="font-family:arial,sans-serif">On Sat, Mar 28, 2015 at 2:52 PM, Matthew Dillon </span><span dir="ltr" style="font-family:arial,sans-serif"><<a href="mailto:dillon@apollo.backplane.com" target="_blank">dillon@apollo.backplane.com</a>></span><span style="font-family:arial,sans-serif"> wrote:</span><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
:<br>
:> a: 1GB boot<br>
<div><div class="h5">:> b: 32GB swap<br>
:> d: * hammer (root and everything else on one hammer filesystem)<br>
:<br>
:fur such a config there is no need to reserve 10% unused.<br>
:just add TRIMming b partition at every boot. swap would rarely be full.<br>
<br>
</div></div> Yes, very true. swap can be TRIMmed on every boot and in most<br>
situations this will leave enough unallocated space.<br>
<br>
In my example I totally forgot to include an 'unused' partition to<br>
hold the reserved area, too, but just having a larger swap partition<br>
and TRIMming it on boot probably works even better.<br>
<br>
The -e option to swapon will trim swap. Hmm.... our rc scripts don't<br>
provide a way to override that to add the -e.<br><span class="HOEnZb"><font color="#888888"><br>
</font></span></blockquote></div><br></div><div class="gmail_extra"><div class="gmail_default" style="font-family:'trebuchet ms',sans-serif;font-size:small">I like this idea. Would I have to use unencrypted swap for this to work?</div><div class="gmail_default" style="font-family:'trebuchet ms',sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:'trebuchet ms',sans-serif;font-size:small">Tim</div></div></div>