本文介绍了libfabric的基本教程, 以及常见代码示例, 包含tcp_socket, libfabric, gpu, dma等代码和示例, 内容基于intel专家的的视频和个人理解, 欢迎一起交流高性能存储, 分布式存储, 网络, rdma等技术
HOTI 热门互联网络技术 视频链接: https://www.youtube.com/watch?v=b-ri1mMLbZ0, 见附录
server端启动:./example_socket客户端连接和发送:./example_socket 192.168.5.6Hello server this is client.
#include <stdio.h>
#include <string.h>
#include <sys/socket.h>
#include <arpa/inet.h>
char *dst_addr = NULL;
int main(int argc, char *argv[])
{
int socket_desc, client_sock, client_size;
struct sockaddr_in server_addr, client_addr;
char server_message[2000], client_message[2000];
dst_addr = inet_addr(argv[1]);
// Clean buffers:
memset(server_message, '\0', sizeof(server_message));
memset(client_message, '\0', sizeof(client_message));
// Create socket:
socket_desc = socket(AF_INET, SOCK_STREAM, 0);
if(socket_desc < 0){
printf("Error while creating socket\n");
return -1;
}
printf("Socket created successfully\n");
// Set port and IP:
server_addr.sin_family = AF_INET;
server_addr.sin_port = "43192";
server_addr.sin_addr.s_addr = inet_addr("127.0.0.1");
if (!dst_addr) {
// Bind to the set port and IP:
if(bind(socket_desc, (struct sockaddr*)&server_addr, sizeof(server_addr))<0){
printf("Couldn't bind to the port\n");
return -1;
}
printf("Binding complete\n");
// Listen for clients:
if(listen(socket_desc, 1) < 0){
printf("Error while listening\n");
return -1;
}
printf("Listening for incoming connections...\n");
// Accept an incoming connection:
client_size = sizeof(client_addr);
client_sock = accept(socket_desc, (struct sockaddr*)&client_addr, &client_size);
if (client_sock < 0){
printf("Can't accept\n");
return -1;
}
printf("Client connected at IP: %s and port: %i\n", inet_ntoa(client_addr.sin_addr), ntohs(client_addr.sin_port));
// Receive client's message:
if (recv(client_sock, client_message, sizeof(client_message), 0) < 0){
printf("Couldn't receive\n");
return -1;
}
printf("Msg from client: %s\n", client_message);
// Respond to client:
strcpy(server_message, "This is the server's message.");
if (send(client_sock, server_message, strlen(server_message), 0) < 0){
printf("Can't send\n");
return -1;
}
}
if (dst_addr) {
// Send connection request to server:
if(connect(socket_desc, (struct sockaddr*)&server_addr, sizeof(server_addr)) < 0){
printf("Unable to connect\n");
return -1;
}
printf("Connected with server successfully\n");
// Get input from the user:
printf("Enter message: ");
gets(client_message);
// Send the message to server:
if(send(socket_desc, client_message, strlen(client_message), 0) < 0){
printf("Unable to send message\n");
return -1;
}
// Receive the server's response:
if(recv(socket_desc, server_message, sizeof(server_message), 0) < 0){
printf("Error while receiving server's msg\n");
return -1;
}
printf("Server's response: %s\n",server_message);
}
// Close the client socket:
close(client_sock);
// Closing the server socket:
close(socket_desc);
return 0;
}
服务端启动: ./example_msg客户端连接发送数据: ./example_msg 192.168.5.6
客户端连接发送数据: ./example_msg 192.168.5.6
https://github.com/ssbandjl/libfabric/blob/main/fabtests/functional/example_msg.c
/*
*
* This software is available to you under the BSD license
* below:
*
* Redistribution and use in source and binary forms, with or
* without modification, are permitted provided that the following
* conditions are met:
*
* - Redistributions of source code must retain the above
* copyright notice, this list of conditions and the following
* disclaimer.
*
* - Redistributions in binary form must reproduce the above
* copyright notice, this list of conditions and the following
* disclaimer in the documentation and/or other materials
* provided with the distribution.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
* EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
* MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
* NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
* BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
* ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
* CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
* SOFTWARE.
*/
#include <stdio.h>
#include <stdlib.h>
#include <getopt.h>
#include <netinet/in.h>
#include <arpa/inet.h>
#include <netdb.h>
#include <rdma/fabric.h>
#include <rdma/fi_domain.h>
#include <rdma/fi_endpoint.h>
#include <rdma/fi_cm.h>
#include <shared.h>
//Build with
//gcc -o example_msg example_msg.c -L<path to libfabric lib> -I<path to libfabric include> -lfabric
//gcc -o example_msg example_msg.c -L/home/xb/project/libfabric/libfabric/build/lib -I/home/xb/project/libfabric/libfabric/build/include -I/home/xb/project/libfabric/libfabric/build/include -lfabric
#define BUF_SIZE 64
char *dst_addr = NULL;
char *port = "9228";
struct fi_info *hints, *info, *fi_pep;
struct fid_fabric *fabric = NULL;
struct fid_domain *domain = NULL;
struct fid_ep *ep = NULL;
struct fid_pep *pep = NULL;
struct fid_cq *cq = NULL;
struct fid_eq *eq = NULL;
struct fi_cq_attr cq_attr = {0};
struct fi_eq_attr eq_attr = {
.wait_obj = FI_WAIT_UNSPEC
};
//const struct sockaddr_in *sin;
char str_addr[INET_ADDRSTRLEN];
int ret;
char buffer[BUF_SIZE];
fi_addr_t fi_addr = FI_ADDR_UNSPEC;
struct fi_eq_cm_entry entry;
uint32_t event;
ssize_t rd;
/* Initializes all basic OFI resources to allow for a server/client to exchange a message */
static int start_client(void)
{
ret = fi_getinfo(FI_VERSION(1,9), dst_addr, port, dst_addr ? 0 : FI_SOURCE,
hints, &info);
if (ret) {
printf("fi_getinfo: %d\n", ret);
return ret;
}
ret = fi_fabric(info->fabric_attr, &fabric, NULL);
if (ret) {
printf("fi_fabric: %d\n", ret);
return ret;
}
ret = fi_eq_open(fabric, &eq_attr, &eq, NULL);
if (ret) {
printf("fi_eq_open: %d\n", ret);
return ret;
}
ret = fi_domain(fabric, info, &domain, NULL);
if (ret) {
printf("fi_domain: %d\n", ret);
return ret;
}
/* Initialize our completion queue. Completion queues are used to report events associated
* with data transfers. In this example, we use one CQ that tracks sends and receives, but
* often times there will be separate CQs for sends and receives.
*/
cq_attr.size = 128;
cq_attr.format = FI_CQ_FORMAT_MSG;
ret = fi_cq_open(domain, &cq_attr, &cq, NULL);
if (ret) {
printf("fi_cq_open error (%d)\n", ret);
return ret;
}
/* Bind our CQ to our endpoint to track any sends and receives that come in or out on that endpoint.
* A CQ can be bound to multiple endpoints but one EP can only have one send CQ and one receive CQ
* (which can be the same CQ).
*/
ret = fi_endpoint(domain, info, &ep, NULL);
if (ret) {
printf("fi_endpoint: %d\n", ret);
return ret;
}
ret = fi_ep_bind(ep, &cq->fid, FI_SEND | FI_RECV);
if (ret) {
printf("fi_ep_bind cq error (%d)\n", ret);
return ret;
}
ret = fi_ep_bind((ep), &(eq)->fid, 0);
if (ret) {
printf("fi_ep_bind: %d\n", ret);
return ret;
}
ret = fi_enable(ep);
if (ret) {
printf("fi_enable: %d\n", ret);
return ret;
}
ret = fi_connect(ep, info->dest_addr, NULL, 0);
if (ret) {
printf("fi_connect: %d\n", ret);
return ret;
}
rd = fi_eq_sread(eq, &event, &entry, sizeof(entry), -1, 0);
if (rd != sizeof(entry)) {
ret = (int) rd;
printf("fi_eq_sread: %d\n", ret);
return ret;
}
return 0;
}
static int start_server(void)
{
const struct sockaddr_in *sin;
/* The first OFI call to happen for initialization is fi_getinfo which queries libfabric
* and returns any appropriate providers that fulfill the hints requirements. Any applicable
* providers will be returned as a list of fi_info structs (&info). Any info can be selected.
* In this test we select the first fi_info struct. Assuming all hints were set appropriately,
* the first fi_info should be most appropriate.
* The flag FI_SOURCE is set for the server to indicate that the address/port refer to source
* information. This is not set for the client because the fields refer to the server, not
* the caller (client). */
/* 初始化时发生的第一个 OFI 调用是 fi_getinfo,它查询 libfabric 并返回满足提示要求的任何适当的提供程序。 任何适用的提供程序都将作为 fi_info 结构 (&info) 列表返回。 可以选择任何信息。 在此测试中,我们选择第一个 fi_info 结构。 假设所有提示均已正确设置,第一个 fi_info 应该是最合适的。 为服务器设置标志FI_SOURCE以指示地址/端口引用源信息。 这不是为客户端设置的,因为这些字段引用服务器,而不是调用者(客户端) */
ret = fi_getinfo(FI_VERSION(1,9), dst_addr, port, dst_addr ? 0 : FI_SOURCE,
hints, &fi_pep);
if (ret) {
printf("fi_getinfo error (%d)\n", ret);
return ret;
}
/* Initialize our fabric. The fabric network represents a collection of hardware and software
* resources that access a single physical or virtual network. All network ports on a system
* that can communicate with each other through their attached networks belong to the same fabric.
*/
ret = fi_fabric(fi_pep->fabric_attr, &fabric, NULL); // 打开fabric, 初始化任何资源前需要打开fabric
if (ret) {
printf("fi_fabric error (%d)\n", ret);
return ret;
}
/* Initialize our endpoint. Endpoints are transport level communication portals which are used to
* initiate and drive communication. There are three main types of endpoints:
* FI_EP_MSG - connected, reliable
* FI_EP_RDM - unconnected, reliable
* FI_EP_DGRAM - unconnected, unreliable
* The type of endpoint will be requested in hints/fi_getinfo. Different providers support different
* types of endpoints. TCP supports only FI_EP_MSG but when used with RxM, can support FI_EP_RDM.
* In this application, we requested TCP and FI_EP_MSG.
*/
ret = fi_eq_open(fabric, &eq_attr, &eq, NULL); // 打开事件队列EQ, 一般用于建连, 收发数据产生的事件
if (ret) {
printf("fi_eq_open: %d\n", ret);
return ret;
}
ret = fi_passive_ep(fabric, fi_pep, &pep, NULL); // 打开被动端点, 常用与服务端监听端口, 支持多个客户端domain连接进来
if (ret) {
printf("fi_passive_ep: %d\n", ret);
return ret;
}
ret = fi_pep_bind(pep, &eq->fid, 0); // 为端点绑定事件队列
if (ret) {
printf("fi_pep_bind %d", ret);
return ret;
}
ret = fi_listen(pep); // 监听端点, 等待客户端连接请求
if (ret) {
printf("fi_listen %d", ret);
return ret;
}
return 0;
}
static int complete_connection(void)
{
rd = fi_eq_sread(eq, &event, &entry, sizeof(entry), -1, 0); // 等待读取客户端触发的服务端事件, 读取事件, 推动进展(驱动程序运转)
if (rd != sizeof entry) {
ret = (int) rd;
printf("fi_eq_sread: %d", ret);
if (ret)
goto err;
}
ret = fi_domain(fabric, info, &domain, NULL); // domain域用于将资源分组, 可基于域来做管理
if (ret) {
printf("fi_domain: %d\n", ret);
return ret;
}
ret = fi_domain_bind(domain, &eq->fid, 0);
if (ret) {
printf("fi_domain_bind: %d\n", ret);
return ret;
}
/*
* Initialize our completion queue. Completion queues are used to report events associated
* with data transfers. In this example, we use one CQ that tracks sends and receives, but
* often times there will be separate CQs for sends and receives.
*/
cq_attr.size = 128;
cq_attr.format = FI_CQ_FORMAT_MSG;
ret = fi_cq_open(domain, &cq_attr, &cq, NULL);
if (ret) {
printf("fi_cq_open error (%d)\n", ret);
return ret;
}
/* Bind our CQ to our endpoint to track any sends and receives that
* come in or out on that endpoint. A CQ can be bound to multiple
* endpoints but one EP can only have one send CQ and one receive CQ
* (which can be the same CQ).
*/
ret = fi_endpoint(domain, info, &ep, NULL); // 用于客户端, 主动端点, 发起建连
if (ret) {
printf("fi_endpoint: %d\n", ret);
return ret;
}
ret = fi_ep_bind(ep, &cq->fid, FI_SEND | FI_RECV);
if (ret) {
printf("fi_ep_bind cq error (%d)\n", ret);
return ret;
}
ret = fi_ep_bind((ep), &(eq)->fid, 0);
if (ret) {
printf("fi_ep_bind: %d\n", ret);
return ret;
}
ret = fi_enable(ep);
if (ret) {
printf("fi_enable: %d", ret);
return ret;
}
ret = fi_accept(ep, NULL, 0);
if (ret) {
printf("fi_accept: %d\n", ret);
return ret;
}
rd = fi_eq_sread(eq, &event, &entry, sizeof(entry), -1, 0);
if (rd != sizeof(entry)) {
ret = (int) rd;
printf("fi_eq_read: %d\n", ret);
return ret;
}
return 0;
err:
if (info)
fi_reject(pep, info->handle, NULL, 0);
return ret;
}
static void cleanup(void)
{
int ret;
/* All OFI resources are cleaned up using the same fi_close(fid) call. */
if (ep) {
ret = fi_close(&ep->fid);
if (ret)
printf("warning: error closing EP (%d)\n", ret);
}
if (pep) {
ret = fi_close(&pep->fid);
if (ret)
printf("warning: error closing PEP (%d)\n", ret);
}
ret = fi_close(&cq->fid);
if (ret)
printf("warning: error closing CQ (%d)\n", ret);
ret = fi_close(&domain->fid);
if (ret)
printf("warning: error closing domain (%d)\n", ret);
ret = fi_close(&eq->fid);
if (ret)
printf("warning: error closing EQ (%d)\n", ret);
ret = fi_close(&fabric->fid);
if (ret)
printf("warning: error closing fabric (%d)\n", ret);
if (info)
fi_freeinfo(info);
if (fi_pep)
fi_freeinfo(fi_pep);
}
/* Post a receive buffer. This call does not ensure a message has been received, just
* that a buffer has been passed to OFI for the next message the provider receives.
* Receives may be directed or undirected using the address parameter. Here, we
* pass in the fi_addr but note that the server has not inserted the client's
* address into its AV, so the address is still FI_ADDR_UNSPEC, indicating that
* this buffer may receive incoming data from any address. An application may
* set this to a real fi_addr if the buffer should only receive data from a certain
* peer.
* When posting a buffer, if the provider is not ready to process messages (because
* of connection initialization for example), it may return -FI_EAGAIN. This does
* not indicate an error, but rather that the application should try again later.
* This is why we almost always wrap sends and receives in a do/while. Some providers
* may need the application to drive progress in order to get out of the -FI_EAGAIN
* loop. To drive progress, the application needs to call fi_cq_read (not necessarily
* reading any completion entries).
*/
static int post_recv(void)
{
int ret;
do {
ret = fi_recv(ep, buffer, BUF_SIZE, NULL, fi_addr, NULL);
if (ret && ret != -FI_EAGAIN) {
printf("error posting recv buffer (%d\n", ret);
return ret;
}
if (ret == -FI_EAGAIN)
(void) fi_cq_read(cq, NULL, 0);
} while (ret);
return 0;
}
/* Post a send buffer. This call does not ensure a message has been sent, just that
* a buffer has been submitted to OFI to be sent. Unlike a receive buffer, a send
* needs a valid fi_addr as input to tell the provider where to send the message.
* Similar to the receive buffer posting porcess, when posting a send buffer, if the
* provider is not ready to process messages, it may return -FI_EAGAIN. This does not
* indicate an error, but rather that the application should try again later. Just like
* the receive, we drive progress with fi_cq_read if this is the case.
*/
static int post_send(void)
{
char *msg = "Hello, server! I am the client you've been waiting for!\0";
int ret;
(void) snprintf(buffer, BUF_SIZE, "%s", msg);
do {
ret = fi_send(ep, buffer, BUF_SIZE, NULL, fi_addr, NULL);
if (ret && ret != -FI_EAGAIN) {
printf("error posting send buffer (%d)\n", ret);
return ret;
}
if (ret == -FI_EAGAIN)
(void) fi_cq_read(cq, NULL, 0);
} while (ret);
return 0;
}
/* Wait for the message to be sent/received using the CQ. fi_cq_read not only drives progress
* but also returns any completed events to notify the application that it can reuse
* the send/recv buffer. The returned completion entry will have fields set to let the application
* know what operation completed. Not all fields will be valid. The fields set will be indicated
* by the cq format (when creating the CQ). In this example, we use FI_CQ_FORMAT_MSG in order to
* use the flags field.
*/
static int wait_cq(void)
{
struct fi_cq_err_entry comp;
int ret;
do {
ret = fi_cq_read(cq, &comp, 1);
if (ret < 0 && ret != -FI_EAGAIN) {
printf("error reading cq (%d)\n", ret);
return ret;
}
} while (ret != 1);
if (comp.flags & FI_RECV)
printf("I received a message!\n");
else if (comp.flags & FI_SEND)
printf("My message got sent!\n");
return 0;
}
static int run(void)
{
int ret;
if (dst_addr) {
printf("Client: send to server %s\n", dst_addr);
ret = post_send();
if (ret)
return ret;
ret = wait_cq();
if (ret)
return ret;
} else {
printf("Server: post buffer and wait for message from client\n");
ret = post_recv();
if (ret)
return ret;
ret = wait_cq();
if (ret)
return ret;
printf("This is the message I received: %s\n", buffer);
}
return 1;
}
int main(int argc, char **argv)
{
int ret;
/* Hints are used to request support for specific features from a provider */
hints = fi_allocinfo(); //
if (!hints)
return EXIT_FAILURE;
/* Server run with no args, client has server's address as an argument */
dst_addr = argv[1];
//Set anything in hints that the application needs
/* Request FI_EP_MSG (reliable datagram) endpoint which will allow us
* to reliably send messages to peers without having to listen/connect/accept. */
hints->ep_attr->type = FI_EP_MSG; // 可靠数据报端点, 类似socket, 但无须执行listen/connect/accept
/* Request basic messaging capabilities from the provider (no tag matching,
* no RMA, no atomic operations) */
hints->caps = FI_MSG;
/* Specifically request the tcp provider for the simple test */
// hints->fabric_attr->prov_name = "tcp"; // 类似socket的, 面向连接的消息类型端点
hints->fabric_attr->prov_name = "ofi_rxm;verbs";
/* Specifically request SOCKADDR_IN address format to simplify addressing for test */
hints->addr_format = FI_SOCKADDR_IN;
/* Default to FI_DELIVERY_COMPLETE which will make sure completions do not get generated
* until our message arrives at the destination. Otherwise, the client might get a completion
* and exit before the server receives the message. This is to make the test simpler */
/* 默认为 FI_DELIVERY_COMPLETE,这将确保在我们的消息到达目的地之前不会生成完成(等待)。 否则,客户端可能会在服务器收到消息之前完成并退出。 这是为了让测试更简单 */
hints->tx_attr->op_flags = FI_DELIVERY_COMPLETE;
//Done setting hints
if (!dst_addr) {
ret = start_server();
if (ret) {
goto out;
return ret;
}
}
ret = dst_addr ? start_client() : complete_connection();
if (ret) {
goto out;
return ret;
}
ret = run();
out:
cleanup();
return ret;
}
verbs
服务端: ./rdmabw-xe -m host
客户端: ./rdmabw-xe -m host -S 1 -t write 192.168.5.6 #都是用主机内存, 完成1字节的远程内存写操作
libfabric, host -> host DMA
服务端: ./fi-rdmabw-xe -m host
客户端: ./fi-rdmabw-xe -m host -S 1 -t write 192.168.5.6 #都是用主机内存, 完成1字节的远程内存写操作
verbs 代码相对位置: fabtests/component/dmabuf-rdma/rdmabw-xe.c
libfabric GPU设备 -> host
服务端: ./fi-rdmabw-xe -m device #使用GPU设备的内存
客户端: ./fi-rdmabw-xe -m host -S 1 -t write 192.168.5.6 #用主机内存, 完成1字节的远程内存写操作
libfabric 代码相对位置: fabtests/component/dmabuf-rdma/fi-rdmabw-xe.c
HOTI 热门互联网络技术
第30届IEEE热互连研讨会: https://hoti.org/
技术视频: https://www.youtube.com/@hoti-hotinterconnectssympo5358/videos
Hot Interconnects 是最先进的硬件和软件架构的研究人员和开发人员的首要国际论坛
Hot Interconnects 是最先进的硬件和软件架构以及各种规模互连网络实现的研究人员和开发人员的首要国际论坛,范围从多核片上互连到系统、集群、数据中心内的互连 和云。 业界和学术界的领导人出席了这一年度会议。 这种氛围提供了大量与该领域前沿人士互动的机会。
主题包括跨领域问题,涵盖计算机系统、网络技术和高性能互连网络的通信协议。 本次会议特别针对这些领域的令人兴奋的新技术和产品创新。
欢迎来到第 30 届 IEEE 热互连研讨会。 HotI30 将以虚拟方式举行。
IEEE Hot Interconnects 是最先进的硬件和软件架构以及各种规模互连网络实现的研究人员和开发人员的首要国际论坛,范围从多核片上互连到系统集群内的互连和数据互连。 中心。 工业界和学术界的领导者出席会议,与该领域最前沿的人士进行互动。
我们的目标是解决数据中心网络和超级计算社区的问题。 我们希望您能加入我们,不仅从内容中受益,还从本次活动始终提供的绝佳交流机会中受益
加速器互连
几乎所有新兴的高价值应用程序,尤其是那些位于边缘的应用程序,都使用加速器而不是 CPU 来实现其基本功能。 此外,在任何规模的集群中,包括边缘集群,都会采用多个加速器来满足此类应用程序的动态需求。 这些加速器可以是同一类型(作为池),也可以是不同类型。 但与 CPU 的情况一样,系统的性能几乎总是受到 I/O 或互连的限制。 因此,我们想要探索加速器的互连如何不仅避免成为瓶颈,更重要的是使加速器协同工作以实现新的应用程序并彻底改变计算架构。 该小组将探讨最具创新性的加速器互连方法,以充分利用这些令人惊叹的加速器的功能
Panda是俄亥俄州立大学计算机科学与工程系的教授和大学杰出学者 。Panda领导 基于网络的计算研究小组。Panda是新成立的耗资 2000 万美元的 NSF-AI 研究所ICICLE 的主任 。
Panda的联系地址是:
计算机科学与工程系 Drreese Lab 785 俄亥俄州立大学 2015 Neil Avenue Columbus, OH-43210, USA | 电话:(614) 292-5199 传真:(614) 292-2911 Twitter:@dhabalkpanda |
---|---|
熊猫教授被公认为俄勒冈州立大学150年历史中的150位创新者之一!
Panda教授的MVAPICH团队是NSF资助的新型Frontera超级计算机的合作伙伴!
Panda 教授被 InsideHPC 授予 HPC 摇滚明星奖。
2023 年 MVAPICH 用户组 (MUG) 会议 将于 2023 年 8 月 21 日至 23 日以混合方式举行。更多详细信息请参见 此处。MUG '22 演示的视频和幻灯片可 在此处获取。
我的团队中的职位: 1)博士后/研究科学家(多名) \2) MPI 软件工程师/程序员(多名) \3) 博士。硕士生(多名) 4)本科生(多名)
高性能计算、高性能网络、大数据分析、深度/机器学习、人工智能、云计算、GPU 和加速器、文件系统和存储以及百亿亿次计算
Dhabaleswar K. (DK) Panda 博士是俄亥俄州立大学计算机科学教授和杰出学者。他获得了博士学位。南加州大学计算机工程专业。他的研究兴趣包括高性能计算、高性能网络 (InfiniBand)、大数据分析(Spark 和 Hadoop)、深度学习、云计算、虚拟化、GPU 和加速器、文件系统和存储以及百亿亿次计算。他在与这些研究领域相关的主要期刊和国际会议上发表了 500 多篇论文。熊猫博士曾担任(或担任)许多国际会议和研讨会的程序主席/联合主席/副主席,包括 HPCAsia '23、CCGRid '22、SCAsia '22、SCAsia '20、ISC '20、CCGrid '18、 ExaComm (15-23)、ESPM2 (15-23)、HPBDC (15-19)、CCGrid '16、PGAS '15、HPBDC '15、HiPC '12、CCGrid '12、HiPC '11、IEEE 集群(集群)'10、超级计算 (SC)'08、ANCS '07、热互连 2007、IPDPS '07 、HiPC '07、热互连 2006、CAC (2001-04)、ICPP '01、CANPC (1997-98) 和 ICPP '98。他曾担任 CCGrid '20、IEEE Micro '19 和 ICPP '06 的总主席/联合主席。他曾担任 IEEE Transactions on Parallel and Distributed Systems (TPDS)、IEEE Transactions on Computers (TC) 和 Journal of Parallel and DistributedComputing (JPDC) 的副主编。目前,他担任《高性能计算 CCF Transactions》的联合主编。他曾担任 190 多个国际会议和研讨会的程序委员会成员。熊猫教授是一位积极主动的演讲者。他曾担任 IEEE 杰出访问者和 IEEE 分会教程演讲者。他在全球范围内发表了大量受邀主题演讲/全体会议、教程和演示。
Panda 博士和他的研究小组成员一直在对现代网络技术进行广泛的研究,包括 InfiniBand、Omni-Path、iWARP、AWS EFA 和 RoCE。他的研究小组目前正在与国家实验室以及领先的 InfiniBand、Omni-Path、iWARP 和 RoCE 公司合作,设计下一代高端系统的各种子系统。 MVAPICH(基于 InfiniBand、iWARP 和 RoCE 的高性能 MPI 和 MPI+PGAS,支持 GPGPU 和虚拟化)软件库是由他的研究小组开发的,目前已被全球 3,300 多个组织(90 个国家/地区)使用。这些软件包使得多个InfiniBand集群进入了最新的TOP500排名。截至 23 年 5 月,仅该项目网站上该软件的下载量就已超过 168 万次。这些软件包还可以与软件堆栈一起提供给网络供应商(InfiniBand、Omni-Path、RoCE、AWS EFA、iWARP 和 Slingshot)、服务器供应商、软件包(OpenHPC 和 Spack)以及 Linux 发行商(例如 RedHat 和 SuSE) )。该软件目前正在为世界排名第七的超级计算机提供动力。
由高性能大数据(HiBD)项目 小组设计和开发的多个用于大数据处理和管理的软件库 可用。其中包括:1) 用于数据科学应用的 MPI4Dask,2) 用于大数据分析应用的 MPI4Spark;3) 支持 RDMA 的 Apache Hadoop 软件库,为 Apache Hadoop 的多个组件(HDFS、MapRce 和 RPC)提供本机 RDMA(InfiniBand Verbs 和 RoCE)支持;4) 支持 RDMA 的 Spark 软件库,提供原生 RDMA(InfiniBand Verbs 和 RoCE)支持;5) RDMA-Memcached 软件库,为 Web 2.0 环境中使用的 Memcached 提供原生 RDMA(InfiniBand Verbs 和 RoCE)支持;5) OSU 高性能大数据基准 (OHB)。这些软件包的示例性能数据和下载说明可从上述网站获得。这些库目前被全球超过 355 个组织(位于 39 个国家/地区)使用。截至 23 年 5 月,超过 47 个,
该小组还一直致力于在现代 HPC 集群和超级计算机上加速深度学习 (DL) 框架(TensorFlow 和 PyTorch)和机器学习 (ML) 框架。 高性能深度学习 (HiDL) 项目网站提供了 MPI 驱动的高性能和可扩展版本 DL/ML 框架的方法 。
熊猫博士领导 基于网络的计算研究小组。该小组的学生和工作人员参与了多个 最先进的研究项目。他的团队成员获得了大量 奖项和荣誉。熊猫博士的研究得到了美国国家科学基金会、美国能源部、美国国防部、俄亥俄州董事会、俄亥俄州发展部以及AMD、ARM、Broadcom、IBM、Intel、Cisco、Cornelis等多个行业的资助Networks、Cray、Oracle、SUN、Mellanox、Microsoft、NVIDIA、Pattern Computer、Rockport Networks、QLogic 和 NetApp。
Panda博士是IEEE Fellow、ACM会员。他是 2022 年 IEEE 查尔斯·巴贝奇奖的获得者 。
关于熊猫博士的更多详细信息可以从他的详细Vita 中获得 。
- [InfiniBand 研究在国会山的演示](http://www.cra.org/govaffairs/blog/archives/000101.html)
- [OSU 软件“增强”超级计算机](http://www.cse.ohio-state./news/news19.shtml)
- [有关该项目的 HPCWire 文章](http://www.tgc.com/hpc-bin/engine.pl?name=/articles/toc121302.html)
- [最近的新闻稿和新闻文章中对该项目的其他引用](http://mvapich.cse.ohio-state./news/)HiBD(高性能大数据)项目HiDL(高性能深度学习)项目研究项目刊物奖项和认可
教学兴趣
我通常教授以下课程。
教学计划(2022-23)
我2022-23学年的教学任务如下:
23 年春季:
22 年秋季:
libfabric教程视频链接: https://www.youtube.com/watch?v=b-ri1mMLbZ0&t=2432s
博客: https://logread.cn | https://blog.csdn.net/ssbandjl | https://cloud.tencent.com/developer/user/5060293/articles
weixin: ssbandjl
公众号: 云原生云
原创声明:本文系作者授权腾讯云开发者社区发表,未经许可,不得转载。
如有侵权,请联系 cloudcommunity@tencent.com 删除。
原创声明:本文系作者授权腾讯云开发者社区发表,未经许可,不得转载。
如有侵权,请联系 cloudcommunity@tencent.com 删除。