<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">On November 5, 2015 at 09:49:27, Alex Williamson (<a href="mailto:alex.l.williamson@gmail.com">alex.l.williamson@gmail.com</a>) wrote:</div><div><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span><div></div><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;"></div></blockquote><div>I don't buy that hugepages allocated at boot perform any different than hugepages allocated dynamically.</div></div></div></div></div></span></blockquote></div><p>I stand corrected. So that means memory fragmentation on the host has no practical performance hit on using hugepages for device assignment? </p><div><p><font face="helvetica, arial">-- </font><br><span data-mce-style="orphans: 2; text-align: -webkit-auto; widows: 2; background-color: #ffffff; color: #020103; font-family: 'Times New Roman', serif;" style="color: rgb(2, 1, 3);"><font face="Calibri"><b>Okky Hendriansyah</b></font></span></p><div></div></div></body></html>