본문으로 이동

Lesson:not a dpu in name only unleashing rdma capable dpus in multi tenant serverless clouds with nadin 7031318c: 두 판 사이의 차이

S3 연구 메모리
← 이전 편집
MCP로 evidence 추가: canonical-paper-v2-7031318c
S3V1 o=s3rm-remediate-v1:dc50e5f1b68ca75f9eda6088b96227491c55048995e6 r=6ebf2fac48bf8fb6d0251b9cde0b1a45 b=2177 e=d08863bfc10a23173f23f662c28a74e216e54d616182aa334fccbb302e4d0084 t=4d5e7d882468228524306907c95dc880 h=401c0c5045bc40a8bdf7cbf562f21046
 
(같은 사용자의 중간 판 3개는 보이지 않습니다)
1번째 줄: 1번째 줄:
{{Lesson
{{Lesson
|title=<nowiki>Not A DPU in Name Only! Unleashing RDMA-capable DPUs in Multi-Tenant Serverless Clouds with NADINO</nowiki>
|title=<nowiki>Not A DPU in Name Only! Unleashing RDMA-capable DPUs in Multi-Tenant Serverless Clouds with NADINO</nowiki>
|question=<nowiki>What problem, design, and evaluation does this paper present?</nowiki>
|question=<nowiki>Can an RDMA-capable DPU provide a zero-copy, isolated data plane for multi-tenant serverless workloads?</nowiki>
|attempt=<nowiki>Paper metadata record; method and artifact details are pending full-text review.</nowiki>
|attempt=<nowiki>NADINO combines DPU RDMA cores, intra-node and CPU-DPU shared memory, plus a DNE reverse proxy for isolation/fairness and HTTP/TCP-to-RDMA conversion.</nowiki>
|context=<nowiki>Venue: EuroSys. Year: 2026.</nowiki>
|context=<nowiki>Venue: EuroSys. Year: 2026.
|observation=<nowiki>Bibliographic metadata only; reported results are pending full-text review.</nowiki>
 
|interpretation=<nowiki>No technical interpretation has been assigned.</nowiki>
Conventional serverless ingress traverses host networking and copies data while underusing DPU RDMA and shared memory.
|reusable_lesson=<nowiki>Pending full-text review.</nowiki>
 
|applicability=<nowiki>distributed and cloud systems; precise applicability is pending full-text review.</nowiki>
Verification: official DOI/publisher abstract and EuroSys program; confidence=high.</nowiki>
|confidence=<nowiki>high</nowiki>
|observation=<nowiki>workloads=serverless ingress/data-plane workloads; baselines=host-centric serverless networking; metrics=requests/s, latency, host CPU cores; results=20.9x RPS; up to 21x lower latency; saves up to 7 CPU cores with 2 DPU cores</nowiki>
|interpretation=<nowiki>The DPU can be the serverless data-plane endpoint rather than a branded NIC offload.</nowiki>
|reusable_lesson=<nowiki>Terminate ingress near RDMA and preserve zero-copy semantics across tenancy boundaries.</nowiki>
|applicability=<nowiki>Multi-tenant serverless clouds with programmable RDMA DPUs.
 
Limits: The paper labels results preliminary; requires compatible DPUs and a redesigned data plane.</nowiki>
|confidence=<nowiki>medium</nowiki>
|evidence=<nowiki>Not A DPU in Name Only! Unleashing RDMA-capable DPUs in Multi-Tenant Serverless Clouds with NADINO. EuroSys 2026.</nowiki>
|evidence=<nowiki>Not A DPU in Name Only! Unleashing RDMA-capable DPUs in Multi-Tenant Serverless Clouds with NADINO. EuroSys 2026.</nowiki>
|record_origin=<nowiki>lab</nowiki>
|record_origin=<nowiki>lab</nowiki>
15번째 줄: 21번째 줄:
|review_state=<nowiki>Draft</nowiki>
|review_state=<nowiki>Draft</nowiki>
|created_at=<nowiki>2026-07-16T15:06:33.635996Z</nowiki>
|created_at=<nowiki>2026-07-16T15:06:33.635996Z</nowiki>
|updated_at=<nowiki>2026-07-18T05:31:00.111254Z</nowiki>
|updated_at=<nowiki>2026-07-18T14:58:47.700163Z</nowiki>
}}
}}


65번째 줄: 71번째 줄:
|added_by=<nowiki>S3ResearchAgent</nowiki>
|added_by=<nowiki>S3ResearchAgent</nowiki>
|added_at=<nowiki>2026-07-18T05:31:00.111254Z</nowiki>
|added_at=<nowiki>2026-07-18T05:31:00.111254Z</nowiki>
}}
{{Lesson evidence verification
|id=<nowiki>verify_484f3c994ac7365a1827</nowiki>
|evidence_id=<nowiki>ev_70d4ddb744da402c</nowiki>
|evidence_digest=<nowiki>49516cf62028574d3484769ba21810af31c9266c82b45bcc0c42a7d49bae5ef8</nowiki>
|verification_basis=<nowiki>metadata_only</nowiki>
|source_identity=<nowiki>R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855</nowiki>
|source_sha256=<nowiki>046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855</nowiki>
|source_locator=<nowiki>보존 파일 objects/sha256/04/046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855</nowiki>
|coverage=<nowiki>보존 객체는 cookie/landing page이므로 서지 위치만 확인했고 본문 주장을 검증하지 못함.</nowiki>
|outcome=<nowiki>inconclusive</nowiki>
|claim_fields=<nowiki>context</nowiki>
|verified_by=<nowiki>S3ResearchAgent</nowiki>
|verified_at=<nowiki>2026-07-18T14:58:47.357844Z</nowiki>
}}
{{Lesson evidence verification
|id=<nowiki>verify_d6b6734cd568f20bfed6</nowiki>
|evidence_id=<nowiki>verified-content-v1-0154</nowiki>
|evidence_digest=<nowiki>8ffcec8be781b2188c94241761d4406e0e74b1ef2615c436fe77c49e641a2375</nowiki>
|verification_basis=<nowiki>metadata_only</nowiki>
|source_identity=<nowiki>R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855</nowiki>
|source_sha256=<nowiki>046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855</nowiki>
|source_locator=<nowiki>보존 파일 objects/sha256/04/046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855</nowiki>
|coverage=<nowiki>보존 객체는 cookie/landing page이므로 서지 위치만 확인했고 본문 주장을 검증하지 못함.</nowiki>
|outcome=<nowiki>inconclusive</nowiki>
|claim_fields=<nowiki>context</nowiki>
|verified_by=<nowiki>S3ResearchAgent</nowiki>
|verified_at=<nowiki>2026-07-18T14:58:47.502363Z</nowiki>
}}
{{Lesson evidence verification
|id=<nowiki>verify_e4dad92e9f9a4e30ab4b</nowiki>
|evidence_id=<nowiki>canonical-paper-v2-7031318c</nowiki>
|evidence_digest=<nowiki>d08863bfc10a23173f23f662c28a74e216e54d616182aa334fccbb302e4d0084</nowiki>
|verification_basis=<nowiki>metadata_only</nowiki>
|source_identity=<nowiki>R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855</nowiki>
|source_sha256=<nowiki>046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855</nowiki>
|source_locator=<nowiki>보존 파일 objects/sha256/04/046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855</nowiki>
|coverage=<nowiki>보존 객체는 cookie/landing page이므로 서지 위치만 확인했고 본문 주장을 검증하지 못함.</nowiki>
|outcome=<nowiki>inconclusive</nowiki>
|claim_fields=<nowiki>context</nowiki>
|verified_by=<nowiki>S3ResearchAgent</nowiki>
|verified_at=<nowiki>2026-07-18T14:58:47.700163Z</nowiki>
}}
}}

2026년 7월 18일 (토) 23:58 기준 최신판

신뢰도 중간 마지막 수정: 2026-07-18T14:58:47.700163Z

메모 편집

제목 Not A DPU in Name Only! Unleashing RDMA-capable DPUs in Multi-Tenant Serverless Clouds with NADINO
궁금했던 점 Can an RDMA-capable DPU provide a zero-copy, isolated data plane for multi-tenant serverless workloads?
해본 것 NADINO combines DPU RDMA cores, intra-node and CPU-DPU shared memory, plus a DNE reverse proxy for isolation/fairness and HTTP/TCP-to-RDMA conversion.
당시 조건 Venue: EuroSys. Year: 2026.

Conventional serverless ingress traverses host networking and copies data while underusing DPU RDMA and shared memory.

Verification: official DOI/publisher abstract and EuroSys program; confidence=high.

실제 결과 workloads=serverless ingress/data-plane workloads; baselines=host-centric serverless networking; metrics=requests/s, latency, host CPU cores; results=20.9x RPS; up to 21x lower latency; saves up to 7 CPU cores with 2 DPU cores
왜 그랬는지 The DPU can be the serverless data-plane endpoint rather than a branded NIC offload.
다음에 기억할 것 Terminate ingress near RDMA and preserve zero-copy semantics across tenancy boundaries.
언제 맞는지 Multi-tenant serverless clouds with programmable RDMA DPUs.

Limits: The paper labels results preliminary; requires compatible DPUs and a redesigned data plane.

신뢰도 중간
관련 자료 Not A DPU in Name Only! Unleashing RDMA-capable DPUs in Multi-Tenant Serverless Clouds with NADINO. EuroSys 2026.
자료 출처 우리 기록
작성자 S3ResearchAgent
처음 작성한 시각 (UTC) 2026-07-16T15:06:33.635996Z
마지막 수정 시각 (UTC) 2026-07-18T14:58:47.700163Z



근거 ev_70d4ddb744da402c: Not A DPU in Name Only! Unleashing RDMA-capable DPUs in Multi-Tenant Serverless Clouds with NADINO. EuroSys 2026.


논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T15:06:34.628937Z
Bibliographic paper record.



근거 verified-content-v1-0154: Shixiong Qi; Songyu Zhang; K. K. Ramakrishnan; Diman Z. Tootaghaj; Hardik Soni; Puneet Sharma. Not A DPU in Name Only! Unleashing RDMA-capable DPUs in Multi-Tenant Serverless Clouds with NADINO. EuroSys, 2026. (원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:59:08.236344Z
Verification: official DOI/publisher abstract and EuroSys program; confidence=high. Canonical title: Not A DPU in Name Only! Unleashing RDMA-capable DPUs in Multi-Tenant Serverless Clouds with NADINO Question: Can an RDMA-capable DPU provide a zero-copy, isolated data plane for multi-tenant serverless workloads? Context: Conventional serverless ingress traverses host networking and copies data while underusing DPU RDMA and shared memory. Method: NADINO combines DPU RDMA cores, intra-node and CPU-DPU shared memory, plus a DNE reverse proxy for isolation/fairness and HTTP/TCP-to-RDMA conversion. Evaluation: workloads=serverless ingress/data-plane workloads; baselines=host-centric serverless networking; metrics=requests/s, latency, host CPU cores; results=20.9x RPS; up to 21x lower latency; saves up to 7 CPU cores with 2 DPU cores Interpretation: The DPU can be the serverless data-plane endpoint rather than a branded NIC offload. Reusable lesson: Terminate ingress near RDMA and preserve zero-copy semantics across tenancy boundaries. Applicability: Multi-tenant serverless clouds with programmable RDMA DPUs. Limits: The paper labels results preliminary; requires compatible DPUs and a redesigned data plane.



근거 canonical-paper-v2-7031318c: Shixiong Qi; Songyu Zhang; K. K. Ramakrishnan; Diman Z. Tootaghaj; Hardik Soni; Puneet Sharma. Not A DPU in Name Only! Unleashing RDMA-capable DPUs in Multi-Tenant Serverless Clouds with NADINO. EuroSys, 2026. (원문 열기)
논문 · 확인 범위: 공식 초록 확인 · S3ResearchAgent · 2026-07-18T05:31:00.111254Z
Verification: official DOI/publisher abstract and EuroSys program; confidence=medium. Canonical title: Not A DPU in Name Only! Unleashing RDMA-capable DPUs in Multi-Tenant Serverless Clouds with NADINO Question: Can an RDMA-capable DPU provide a zero-copy, isolated data plane for multi-tenant serverless workloads? Context: Conventional serverless ingress traverses host networking and copies data while underusing DPU RDMA and shared memory. Method: NADINO combines DPU RDMA cores, intra-node and CPU-DPU shared memory, plus a DNE reverse proxy for isolation/fairness and HTTP/TCP-to-RDMA conversion. Evaluation: workloads=serverless ingress/data-plane workloads; baselines=host-centric serverless networking; metrics=requests/s, latency, host CPU cores; results=20.9x RPS; up to 21x lower latency; saves up to 7 CPU cores with 2 DPU cores Interpretation: The DPU can be the serverless data-plane endpoint rather than a branded NIC offload. Reusable lesson: Terminate ingress near RDMA and preserve zero-copy semantics across tenancy boundaries. Applicability: Multi-tenant serverless clouds with programmable RDMA DPUs. Limits: The paper labels results preliminary; requires compatible DPUs and a redesigned data plane.



자료 검증 verify_484f3c994ac7365a1827: ev_70d4ddb744da402c · 판단 보류
확인 범위: 서지정보만 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:47.357844Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855 / 위치: 보존 파일 objects/sha256/04/046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855
보존 객체는 cookie/landing page이므로 서지 위치만 확인했고 본문 주장을 검증하지 못함.



자료 검증 verify_d6b6734cd568f20bfed6: verified-content-v1-0154 · 판단 보류
확인 범위: 서지정보만 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:47.502363Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855 / 위치: 보존 파일 objects/sha256/04/046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855
보존 객체는 cookie/landing page이므로 서지 위치만 확인했고 본문 주장을 검증하지 못함.



자료 검증 verify_e4dad92e9f9a4e30ab4b: canonical-paper-v2-7031318c · 판단 보류
확인 범위: 서지정보만 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:47.700163Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855 / 위치: 보존 파일 objects/sha256/04/046b61c4c93e9f9a45977672aeb4eebf20629bd871bcdd20755f73abe772d855
보존 객체는 cookie/landing page이므로 서지 위치만 확인했고 본문 주장을 검증하지 못함.

원본 주소 "https://s3wiki.yonsei.ac.kr/index.php?title=Lesson:not_a_dpu_in_name_only_unleashing_rdma_capable_dpus_in_multi_tenant_serverless_clouds_with_nadin_7031318c&oldid=2178"