|
563 | 563 | <!–– Slide12 ––>
|
564 | 564 | <section> smartNICs with Storage
|
565 | 565 | <aside class="notes">
|
566 |
| -I talked mostly about the data traffic so far and using smartNICs with the data traffic. |
567 |
| -smartNICs make sense in a lot of cases, storage, video, big data, security. In the storage case, they can be used to be used to accelerate storage apps and security, like encrypting data on the disk. |
568 |
| -Using smartNICs with NVMeOF you can disagrate compute from storage and you can get local storage performance across the network, that is very close performance between local storage and remote storage. Basically you attach a block device to your VM and acessing it is as fast as if it was local. |
569 |
| -NVMeOF maintains the high performance of a local nvme SSD. |
570 |
| - |
571 |
| -Many applications moving to cloud today are probably not in high demand of high speed access to disks, because they were written for HDDs to begin with. |
572 |
| -But in the future for sure |
573 |
| -smartNICs with Storage - TO BE ADDED |
574 |
| -Using smartNICs for NVMe termination |
575 |
| -NVMe ov TCP , Roce v2 |
576 |
| -- advance to next slide - |
| 566 | +<br>I talked mostly about the data traffic so far and using smartNICs with the data traffic. |
| 567 | +<br><br>smartNICs make sense in a lot of cases, storage, video, big data, security. In the storage case, they can be used to be used to accelerate storage apps and security, like encrypting data on the disk. |
| 568 | +<br>Using smartNICs with NVMeOF you can disagrate compute from storage and you can get local storage performance across the network, that is very close performance between local storage and remote storage. |
| 569 | +<br>Basically you attach a block device to your VM and acessing it is as fast as if it was local. |
| 570 | +<br>NVMeOF maintains the high performance of a local nvme SSD. |
| 571 | +<br><br>Many applications moving to cloud today are probably not in high demand of high number of IOPS, because they were written for HDDs to begin with. |
| 572 | +<br>But smartNICs with storage will be relevant in the future. |
| 573 | + |
577 | 574 | </aside>
|
578 | 575 | </section>
|
579 | 576 | <!–– Slide13 ––>
|
580 |
| - <section> Ericsson customers are running on Openstack. |
| 577 | + <section> Ericsson customers that are running on Openstack. |
581 | 578 | <aside class="notes">
|
582 | 579 | List some operators, the olympics in Japan with docomo, etc - TO BE ADDED
|
583 | 580 | - advance to next slide -
|
|
599 | 596 | <br>Datacenters today?
|
600 | 597 | <br>Stacked up "desktop" computers filled with ... air?
|
601 | 598 | <aside class="notes">
|
602 |
| -2. Secondly, it's my desire to leave you with a thought. |
603 |
| -I came to the realization that most of the things we learn are provisional and in consequence they are open to recantation and refutation. I enjoy this path of questioning everything, why do we do things a certain way. |
604 |
| -In 2001 my first job was sysadmin working for a big Eastern European Internet Service Provider |
| 599 | +<br>Secondly, it's my desire to leave you with a thought. |
| 600 | +<br>I came to the realization that most of the things we learn are provisional and in consequence they are open to recantation and refutation. I enjoy this path of questioning everything, why do we do things a certain way. |
| 601 | +<br><br>In 2001 my first job was sysadmin working for a big Eastern European Internet Service Provider |
605 | 602 | Many customers asked to move their web servers and mail servers on our premises.
|
606 |
| -It was because their services would access directly the big pipe and we had a generator. 2001 Eastern European country meant many power outages, |
| 603 | +It was because their services would access directly the big pipe and we had a generator. 2001 Eastern Europe meant lots of power outages ... daily. |
607 | 604 |
|
608 |
| -They would bring desktop tower PCs we had a room with tables against the wall and we lined up the towers on these tables. Soon enough, we ran out of physical space on those tables and bought racks. We asked customers to buy rackable servers in order to host with us, then we ran out of space again and somewhere 2005 we started using VMs. |
| 605 | +<br><br>They would bring desktop tower PCs we had a room with tables against the wall and we lined up the towers on these tables. Soon enough, we ran out of physical space on those tables and bought racks. We asked customers to buy rackable servers in order to host with us, then we ran out of space again and somewhere 2005 we started using VMs. |
609 | 606 | Fast forward, today our datacenters are collections of those stacked boxes that used to be desktop computers. To me, this is insane, does it make any sense to you? Should we go down the timeline of computer history and have racks of disks and racks of memory and CPU and racks of NICs?
|
610 | 607 | - advance to next slide -
|
611 | 608 | </aside>
|
612 | 609 | </section>
|
613 | 610 |
|
614 |
| -<!–– SlideX ––> |
615 |
| - <section> |
616 |
| -<p>Demo</p> |
617 |
| - <aside class="notes"> |
618 |
| -1. e.g. dc348 show cpu allocation cpu_layout.py |
619 |
| -2. dc348 show lshw -C network -businfo on normal compute to show the driver for the card |
620 |
| -3. show driver for smartNIC native virtio |
621 |
| -4. ebpf exercise |
622 |
| - </aside> |
623 |
| - </section> |
624 |
| - |
625 | 611 |
|
626 |
| -<!–– SlideX ––> |
627 |
| - <section> To DELETE |
628 |
| - <tr> |
629 |
| - <th><img src="pics/slide8_intel-ericsson-logo.jpg" width=100% height=100%></th> |
630 |
| - </tr> |
631 |
| - <aside class="notes"> |
632 |
| - At Ericsson, |
633 |
| - </aside> |
634 |
| - </section> |
635 |
| -<!–– SlideX ––> |
636 |
| - <section data-background-color="#FFC0CB">To DELETE |
637 |
| - <tr> |
638 |
| - <th><img src="pics/me.jpg" width=27% height=27%></th> |
639 |
| - <th><img src="pics/j.jpg" width=35% height=35%></th> |
640 |
| - </tr> |
641 |
| - </section> |
642 |
| - <section data-background-color="#FFC0CB">To DELETE |
643 |
| - <p> |
644 |
| - DPDK/SPDK |
645 |
| - </p> |
646 |
| - </section> |
647 |
| - <section data-background-color="#FFC0CB" >To DELETE |
648 |
| - <p> |
649 |
| - <img src="pics/sn.png" width=75% height=75%> |
650 |
| - |
651 |
| - </p> |
652 |
| - </section> |
653 |
| - <section data-background-color="#FFC0CB" >To DELETE |
654 |
| - <p> |
655 |
| - <img src="pics/kernel-diag-ascii.svg" width=35% height=35%> |
656 |
| - </p> |
657 |
| - </section> |
658 |
| - <section data-background-color="#FFC0CB">To DELETE |
659 |
| - <p> |
660 |
| - PCI bifurcation |
661 |
| - </p> |
662 |
| - </section> |
663 |
| - <section data-background-color="#FFC0CB">To DELETE |
664 |
| - <p> |
665 |
| - <img src="pics/termtosvg_5xxaxp7l.svg" width=60% height=60%> |
666 |
| - </p> |
667 |
| - </section> |
668 | 612 | </div>
|
669 | 613 | </div>
|
670 | 614 |
|
|
0 commit comments