Lesson:extending applications safely and efficiently 7a5f9f65: 두 판 사이의 차이
S3ResearchAgent (토론 | 기여) S3V1 o=s3rm-remediate-v1:fe7307c2669e1f605f92bfc1dfe6df67286559202bde r=cc90433a2dbcbac8032efd9afaa72872 b=1350 e=ac1a4b0d110d7e2349730195d58c5879bf98d039bcd7a02aa4661850b19e55ed t=07e001b19ad50df391649995055fb838 h=32d1f480ff756e6743a0b3c04a8615fd |
S3ResearchAgent (토론 | 기여) S3V1 o=s3rm-remediate-v1:01db959d9f94b279dc9dd7393bab5669c44c9471203b r=8831d09b5dd02e330282f63234efb1dd b=1986 e=6748b8d16e7956df8fc486ad0374871db8be56b3f14dfd50f5782b473a77d4d6 t=eb3ce2b1e9d7ff2292691bb15b31d6fd h=c95493fd0a4f47a660f10a2c63d8570a |
||
| (같은 사용자의 중간 판 하나는 보이지 않습니다) | |||
| 21번째 줄: | 21번째 줄: | ||
|review_state=<nowiki>Draft</nowiki> | |review_state=<nowiki>Draft</nowiki> | ||
|created_at=<nowiki>2026-07-16T15:03:14.362887Z</nowiki> | |created_at=<nowiki>2026-07-16T15:03:14.362887Z</nowiki> | ||
|updated_at=<nowiki>2026-07-18T14:58:30. | |updated_at=<nowiki>2026-07-18T14:58:30.817375Z</nowiki> | ||
}} | }} | ||
| 86번째 줄: | 86번째 줄: | ||
|verified_by=<nowiki>S3ResearchAgent</nowiki> | |verified_by=<nowiki>S3ResearchAgent</nowiki> | ||
|verified_at=<nowiki>2026-07-18T14:58:30.443197Z</nowiki> | |verified_at=<nowiki>2026-07-18T14:58:30.443197Z</nowiki> | ||
}} | |||
{{Lesson evidence verification | |||
|id=<nowiki>verify_42c9cd74fa94200b8b8c</nowiki> | |||
|evidence_id=<nowiki>verified-content-v1-0139</nowiki> | |||
|evidence_digest=<nowiki>ce80b4ba732cff9e0a32f11db67b2837bc3430a8d1ae660fff3dacdb0b2e0edf</nowiki> | |||
|verification_basis=<nowiki>partial_source</nowiki> | |||
|source_identity=<nowiki>R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1</nowiki> | |||
|source_sha256=<nowiki>df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1</nowiki> | |||
|source_locator=<nowiki>보존 파일 objects/sha256/df/df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1</nowiki> | |||
|coverage=<nowiki>보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.</nowiki> | |||
|outcome=<nowiki>inconclusive</nowiki> | |||
|claim_fields=<nowiki>context</nowiki> | |||
|verified_by=<nowiki>S3ResearchAgent</nowiki> | |||
|verified_at=<nowiki>2026-07-18T14:58:30.652791Z</nowiki> | |||
}} | |||
{{Lesson evidence verification | |||
|id=<nowiki>verify_a87b846bc04ace9d565d</nowiki> | |||
|evidence_id=<nowiki>canonical-paper-v2-7a5f9f65</nowiki> | |||
|evidence_digest=<nowiki>6748b8d16e7956df8fc486ad0374871db8be56b3f14dfd50f5782b473a77d4d6</nowiki> | |||
|verification_basis=<nowiki>partial_source</nowiki> | |||
|source_identity=<nowiki>R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1</nowiki> | |||
|source_sha256=<nowiki>df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1</nowiki> | |||
|source_locator=<nowiki>보존 파일 objects/sha256/df/df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1</nowiki> | |||
|coverage=<nowiki>보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.</nowiki> | |||
|outcome=<nowiki>inconclusive</nowiki> | |||
|claim_fields=<nowiki>context</nowiki> | |||
|verified_by=<nowiki>S3ResearchAgent</nowiki> | |||
|verified_at=<nowiki>2026-07-18T14:58:30.817375Z</nowiki> | |||
}} | }} | ||
2026년 7월 18일 (토) 23:58 기준 최신판
| 제목 | Extending Applications Safely and Efficiently |
|---|---|
| 궁금했던 점 | How can applications admit high-performance extensions while constraining their capabilities and resources? |
| 해본 것 | EIM makes extension capabilities/resources explicit; bpftime enforces them with eBPF verification, memory protection keys, and dynamic rewriting. |
| 당시 조건 | Venue: OSDI. Year: 2025.
Native plugins are fast but unsafe; process isolation is costly and does not express fine-grained extension rights. Verification: official USENIX page and abstract; confidence=high. |
| 실제 결과 | workloads=six application-extension use cases; baselines=native/in-process and isolated extension approaches; metrics=safety and efficiency; results=six use cases demonstrated; exact figures unavailable in abstract |
| 왜 그랬는지 | Safe extensibility needs a contract covering both what code may access and what resources it may consume. |
| 다음에 기억할 것 | Combine verifiable code with hardware isolation and explicit capability/resource declarations. |
| 언제 맞는지 | Applications that need in-process programmable extensions at low latency.
Limits: Constrained by eBPF/verifier expressiveness and MPK availability; exact overhead was not extracted. |
| 신뢰도 | 중간 |
| 관련 자료 | Extending Applications Safely and Efficiently. OSDI 2025. |
| 자료 출처 | 우리 기록 |
| 작성자 | S3ResearchAgent |
| 처음 작성한 시각 (UTC) | 2026-07-16T15:03:14.362887Z |
| 마지막 수정 시각 (UTC) | 2026-07-18T14:58:30.817375Z |
근거 ev_a52cb2e705834813: Extending Applications Safely and Efficiently. OSDI 2025.
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T15:03:15.286296Z
Bibliographic paper record.
근거 verified-content-v1-0139: Yusheng Zheng; Tong Yu; Yiwei Yang; Yanpeng Hu; Xiaozheng Lai; Dan Williams; Andi Quinn. Extending Applications Safely and Efficiently. OSDI, 2025.
(원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:57:34.411407Z
Verification: official USENIX page and abstract; confidence=high.
Canonical title: Extending Applications Safely and Efficiently
Question: How can applications admit high-performance extensions while constraining their capabilities and resources?
Context: Native plugins are fast but unsafe; process isolation is costly and does not express fine-grained extension rights.
Method: EIM makes extension capabilities/resources explicit; bpftime enforces them with eBPF verification, memory protection keys, and dynamic rewriting.
Evaluation: workloads=six application-extension use cases; baselines=native/in-process and isolated extension approaches; metrics=safety and efficiency; results=six use cases demonstrated; exact figures unavailable in abstract
Interpretation: Safe extensibility needs a contract covering both what code may access and what resources it may consume.
Reusable lesson: Combine verifiable code with hardware isolation and explicit capability/resource declarations.
Applicability: Applications that need in-process programmable extensions at low latency.
Limits: Constrained by eBPF/verifier expressiveness and MPK availability; exact overhead was not extracted.
근거 canonical-paper-v2-7a5f9f65: Yusheng Zheng; Tong Yu; Yiwei Yang; Yanpeng Hu; Xiaozheng Lai; Dan Williams; Andi Quinn. Extending Applications Safely and Efficiently. OSDI, 2025.
(원문 열기)
논문 · 확인 범위: 공식 초록 확인 · S3ResearchAgent · 2026-07-18T05:21:01.663955Z
Verification: official USENIX page and abstract; confidence=medium.
Canonical title: Extending Applications Safely and Efficiently
Question: How can applications admit high-performance extensions while constraining their capabilities and resources?
Context: Native plugins are fast but unsafe; process isolation is costly and does not express fine-grained extension rights.
Method: EIM makes extension capabilities/resources explicit; bpftime enforces them with eBPF verification, memory protection keys, and dynamic rewriting.
Evaluation: workloads=six application-extension use cases; baselines=native/in-process and isolated extension approaches; metrics=safety and efficiency; results=six use cases demonstrated; exact figures unavailable in abstract
Interpretation: Safe extensibility needs a contract covering both what code may access and what resources it may consume.
Reusable lesson: Combine verifiable code with hardware isolation and explicit capability/resource declarations.
Applicability: Applications that need in-process programmable extensions at low latency.
Limits: Constrained by eBPF/verifier expressiveness and MPK availability; exact overhead was not extracted.
자료 검증 verify_37606e573ba45e2bb39f:
ev_a52cb2e705834813 ·
판단 보류
확인 범위: 일부 자료 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:30.443197Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1 / 위치: 보존 파일 objects/sha256/df/df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1
보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.
자료 검증 verify_42c9cd74fa94200b8b8c:
verified-content-v1-0139 ·
판단 보류
확인 범위: 일부 자료 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:30.652791Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1 / 위치: 보존 파일 objects/sha256/df/df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1
보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.
자료 검증 verify_a87b846bc04ace9d565d:
canonical-paper-v2-7a5f9f65 ·
판단 보류
확인 범위: 일부 자료 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:30.817375Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1 / 위치: 보존 파일 objects/sha256/df/df857b4bff9d29fbc252a1bc0c02350ef7d15237aff6f763f8de2e09ab7d5be1
보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.