<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>Sorry... I guess our discussion here is in line with the "good practices" discussion. For a long time I see a lot of mentions on having a front-end and a back-end network when dealing with distributed file systems like Gluster and Ceph. What I would like
to here from those who already implemented oVirt on the field is "what is the real life" approach for good performance as large file/memory transfers will strongly benefit from having a big MTU. However, big MTU must be driven correctly otherwise you may end-up
having the problem we are discussing.<br>
</p>
<br>
Moacir<br>
<br>
<div style="color: rgb(49, 55, 57);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Moacir Ferreira <moacirferreira@hotmail.com><br>
<b>Sent:</b> Tuesday, August 8, 2017 3:16 PM<br>
<b>To:</b> Fabrice Bacchella<br>
<b>Cc:</b> users@ovirt.org<br>
<b>Subject:</b> Re: [ovirt-users] Users Digest, Vol 71, Issue 37</font>
<div> </div>
</div>
<div>
<div id="divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Exactly Fabrice! In this case the router will fragment the "bigger" MTU to fit the "smaller" MTU but only when the DF is not set. However, fragmentation on routers are made by the control plane, meaning you will overload the router CPU doing too much fragmentation.
On a good NIC the announced MTU to the IP stack is very big (like 64Kb) because the off-load engine will fragment this very large MTU and send it. But on this kind of NIC the fragmentation is done by dedicated AISCs that does not require any CPU intervention
to do it. Just give it a try... Assemble a lab using Linux and you will see what I am trying to explain.<br>
</p>
<br>
Moacir<br>
<br>
<div style="color:rgb(49,55,57)">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Fabrice Bacchella <fabrice.bacchella@orange.fr><br>
<b>Sent:</b> Tuesday, August 8, 2017 2:50 PM<br>
<b>To:</b> Moacir Ferreira<br>
<b>Cc:</b> users@ovirt.org<br>
<b>Subject:</b> Re: [ovirt-users] Users Digest, Vol 71, Issue 37</font>
<div> </div>
</div>
<div><br class="">
<div>
<blockquote type="cite" class="">
<div class="">Le 8 août 2017 à 14:53, Moacir Ferreira <<a href="mailto:moacirferreira@hotmail.com" class="">moacirferreira@hotmail.com</a>> a écrit :</div>
<br class="Apple-interchange-newline">
<div class="">
<div id="divtagdefaultwrapper" dir="ltr" class="" style="font-style: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; font-size:12pt; font-family:Calibri,Helvetica,sans-serif">
<div class="" style="margin-top:0px; margin-bottom:0px">But if you receive a 9000 MTU frame on an "input" interface that results sending it out on an interface of a 1500 MTU, then if you set DF bit the frame will just be dropped by the router.</div>
</div>
</div>
</blockquote>
<br class="">
</div>
The frame will be dropped and the router will send an ICMP message "packet to big" to the sender, it's network stack will received that, learn that the PMTU is lower and try with smaller fragment, see <a href="https://en.wikipedia.org/wiki/Path_MTU_Discovery" class="">https://en.wikipedia.org/wiki/Path_MTU_Discovery</a>.
<div class=""><br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>