dsdf

Author: Elena Crenguta Lindqvist

itnot/index.html

@@ -70,7 +70,7 @@
 					</tr>
 					<tr>
 					<p>
-					    <th>40% of all mobile traffic crunching data</th>	
+					    <th>40% of all mobile traffic data</th>	
 					</p>
 				        </tr>
 					<aside class="notes">
@@ -240,13 +240,31 @@
                                 </section>
 <!––  SlideX ––>
                                 <section> 
-<p>Picture ovs CPU allocation, cpuisol </p>                                  
+                                        <tr>
+                                            <th><img src="pics/cpuisol1.png" width=90% height=90%></th>
+                                        </tr>                                        
+                                        <aside class="notes">                                      
+Here you can see the CPUs allocated to ovs under nohz_full ( confirmed with /etc/default PMDs)
+nohz_full=cpulist
+The nohz_full parameter is used to treat a list of CPUs differently, with respect to timer ticks. If a CPU is listed as a nohz_full CPU and there is only one runnable task on the CPU, then the kernel will stop sending timer ticks to that CPU, so more time may be spent running the application and less time spent servicing interrupts and context switching.
+https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_for_real_time/7/html/tuning_guide/isolating_cpus_using_tuned-profiles-realtime
+
+2 for hostOS
+2 + threads for ovs
+								</aside>
+                                </section>
+
+<!––  SlideX ––>
+                                <section> 
+                                        <tr>
+                                            <th><img src="pics/cpuisol.png" width=99% height=99%></th>
+                                        </tr>                                        
                                         <aside class="notes">                                      
-Here you can see the CPUs allocated to ovs, in my case X number of CPUs, the one in cpuisol are the CPUs that will be used by nova
-the ones missing are two? for host OS and rest for OVS
-in yaml file also 
+2 for hostOS
+4 + threads for ovs
 								</aside>
                                 </section>
+
 
 <!––  Slide10 ––>
                                 <section>   <p>Ironic Neutron Cyborg</p>
@@ -578,6 +596,19 @@
 - advance to next slide -
                                         </aside>
                                 </section>
+
+<!––  SlideX ––>
+                                <section> 
+<p>Demo</p>                                  
+                                        <aside class="notes">                                      
+1. e.g. dc348 show cpu allocation cpu_layout.py
+2. dc348 show lshw -C network -businfo on normal compute to show the driver for the card
+3. show driver for smartNIC native virtio 
+4. ebpf exercise 
+								</aside>
+                                </section>
+
+
 <!––  SlideX ––>	
 				<section> To DELETE
 					<tr>

itnot/notes

@@ -264,3 +264,4 @@ https://www.youtube.com/watch?v=Y103CWBa1BI XDP talk
 https://blogs.msdn.microsoft.com/peterwie/2006/03/09/what-is-dma-part-4-common-buffer/
 https://opensourceforu.com/2016/10/network-performance-monitoring/
 https://www.youtube.com/watch?v=54VemA4tLkY NVMeOF
+https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_for_real_time/7/html/tuning_guide/isolating_cpus_using_tuned-profiles-realtime isolcpu