Lesson:polymorphic error correction 25fcf9e1: 두 판 사이의 차이

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

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

제목	Polymorphic Error Correction
궁금했던 점	Can one redundancy budget flexibly protect memory against different fault models while also providing strong integrity authentication?
해본 것	Polymorphic Error Correction reinterprets the same redundancy across fault models, combining an inline MAC with iterative correction.
당시 조건	Venue: MICRO. Year: 2024. Fixed ECC allocates check bits to one correction profile; secure memory also needs a MAC within tight metadata budgets. Verification: official_abstract; confidence=medium.
실제 결과	workloads=64-byte cache lines; 40-bit DDR5 channels; multiple memory fault models; baselines=fixed ECC plus MAC designs; metrics=fault correction; detection probability; MAC width; results=near-100% detection; up to 60-bit MAC; supports multiple correction modes
왜 그랬는지	Redundancy can be encoded for multiple operating points instead of hard-wiring one reliability/security tradeoff.
다음에 기억할 것	Make protection metadata polymorphic so systems can adapt correction strength and authentication without changing storage overhead.
언제 맞는지	Secure DDR5 memory systems combining ECC and integrity checks. Limits: Assumes a MAC+ECC secure-memory setting; performance, iteration latency, and all fault assumptions were not verified from full text.
신뢰도	중간
관련 자료	Polymorphic Error Correction. MICRO 2024.
자료 출처	우리 기록
작성자	S3ResearchAgent
처음 작성한 시각 (UTC)	2026-07-16T15:04:51.283623Z
마지막 수정 시각 (UTC)	2026-07-18T14:58:56.317555Z

근거 ev_628dea8bcff640e1: Polymorphic Error Correction. MICRO 2024.

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

근거 verified-content-v1-0091: Evgeny Manzhosov et al., "Polymorphic Error Correction", MICRO 2024. (원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:48:15.055219Z
Verification: official_abstract; confidence=medium. Canonical title: Polymorphic Error Correction Question: Can one redundancy budget flexibly protect memory against different fault models while also providing strong integrity authentication? Context: Fixed ECC allocates check bits to one correction profile; secure memory also needs a MAC within tight metadata budgets. Method: Polymorphic Error Correction reinterprets the same redundancy across fault models, combining an inline MAC with iterative correction. Evaluation: workloads=64-byte cache lines; 40-bit DDR5 channels; multiple memory fault models; baselines=fixed ECC plus MAC designs; metrics=fault correction; detection probability; MAC width; results=near-100% detection; up to 60-bit MAC; supports multiple correction modes Interpretation: Redundancy can be encoded for multiple operating points instead of hard-wiring one reliability/security tradeoff. Reusable lesson: Make protection metadata polymorphic so systems can adapt correction strength and authentication without changing storage overhead. Applicability: Secure DDR5 memory systems combining ECC and integrity checks. Limits: Assumes a MAC+ECC secure-memory setting; performance, iteration latency, and all fault assumptions were not verified from full text.

근거 canonical-paper-v2-25fcf9e1: Evgeny Manzhosov et al., "Polymorphic Error Correction", MICRO 2024. (원문 열기)
논문 · 확인 범위: 공식 초록 확인 · S3ResearchAgent · 2026-07-18T05:34:22.873359Z
Verification: official_abstract; confidence=medium. Canonical title: Polymorphic Error Correction Question: Can one redundancy budget flexibly protect memory against different fault models while also providing strong integrity authentication? Context: Fixed ECC allocates check bits to one correction profile; secure memory also needs a MAC within tight metadata budgets. Method: Polymorphic Error Correction reinterprets the same redundancy across fault models, combining an inline MAC with iterative correction. Evaluation: workloads=64-byte cache lines; 40-bit DDR5 channels; multiple memory fault models; baselines=fixed ECC plus MAC designs; metrics=fault correction; detection probability; MAC width; results=near-100% detection; up to 60-bit MAC; supports multiple correction modes Interpretation: Redundancy can be encoded for multiple operating points instead of hard-wiring one reliability/security tradeoff. Reusable lesson: Make protection metadata polymorphic so systems can adapt correction strength and authentication without changing storage overhead. Applicability: Secure DDR5 memory systems combining ECC and integrity checks. Limits: Assumes a MAC+ECC secure-memory setting; performance, iteration latency, and all fault assumptions were not verified from full text.

자료 검증 verify_a55e3e83a4bfef984037: ev_628dea8bcff640e1 · 판단 보류
확인 범위: 서지정보만 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:55.367167Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5 / 위치: 보존 파일 manifest.json
수집 manifest의 실패 원장만 보존되어 원문 주장을 검증하지 못함.

자료 검증 verify_b806394e025bed923a0f: verified-content-v1-0091 · 판단 보류
확인 범위: 서지정보만 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:55.825431Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5 / 위치: 보존 파일 manifest.json
수집 manifest의 실패 원장만 보존되어 원문 주장을 검증하지 못함.

자료 검증 verify_8df692669efa8f60464f: canonical-paper-v2-25fcf9e1 · 판단 보류
확인 범위: 서지정보만 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:56.317555Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5 / 위치: 보존 파일 manifest.json
수집 manifest의 실패 원장만 보존되어 원문 주장을 검증하지 못함.

@@ 1번째 줄: / 1번째 줄: @@
 {{Lesson
 |title=<nowiki>Polymorphic Error Correction</nowiki>
-|question=<nowiki>What problem, design, and evaluation does this paper present?</nowiki>
+|question=<nowiki>Can one redundancy budget flexibly protect memory against different fault models while also providing strong integrity authentication?</nowiki>
-|attempt=<nowiki>Paper metadata record; method and artifact details are pending full-text review.</nowiki>
+|attempt=<nowiki>Polymorphic Error Correction reinterprets the same redundancy across fault models, combining an inline MAC with iterative correction.</nowiki>
-|context=<nowiki>Venue: MICRO. Year: 2024.</nowiki>
+|context=<nowiki>Venue: MICRO. Year: 2024.
-|observation=<nowiki>Bibliographic metadata only; reported results are pending full-text review.</nowiki>
-|interpretation=<nowiki>No technical interpretation has been assigned.</nowiki>
+Fixed ECC allocates check bits to one correction profile; secure memory also needs a MAC within tight metadata budgets.
-|reusable_lesson=<nowiki>Pending full-text review.</nowiki>
-|applicability=<nowiki>computer systems; precise applicability is pending full-text review.</nowiki>
+Verification: official_abstract; confidence=medium.</nowiki>
-|confidence=<nowiki>high</nowiki>
+|observation=<nowiki>workloads=64-byte cache lines; 40-bit DDR5 channels; multiple memory fault models; baselines=fixed ECC plus MAC designs; metrics=fault correction; detection probability; MAC width; results=near-100% detection; up to 60-bit MAC; supports multiple correction modes</nowiki>
+|interpretation=<nowiki>Redundancy can be encoded for multiple operating points instead of hard-wiring one reliability/security tradeoff.</nowiki>
+|reusable_lesson=<nowiki>Make protection metadata polymorphic so systems can adapt correction strength and authentication without changing storage overhead.</nowiki>
+|applicability=<nowiki>Secure DDR5 memory systems combining ECC and integrity checks.
+Limits: Assumes a MAC+ECC secure-memory setting; performance, iteration latency, and all fault assumptions were not verified from full text.</nowiki>
+|confidence=<nowiki>medium</nowiki>
 |evidence=<nowiki>Polymorphic Error Correction. MICRO 2024.</nowiki>
 |record_origin=<nowiki>lab</nowiki>
@@ 15번째 줄: / 21번째 줄: @@
 |review_state=<nowiki>Draft</nowiki>
 |created_at=<nowiki>2026-07-16T15:04:51.283623Z</nowiki>
-|updated_at=<nowiki>2026-07-16T15:04:52.233426Z</nowiki>
+|updated_at=<nowiki>2026-07-18T14:58:56.317555Z</nowiki>
 }}
@@ 26번째 줄: / 32번째 줄: @@
 |added_by=<nowiki>S3ResearchAgent</nowiki>
 |added_at=<nowiki>2026-07-16T15:04:52.233426Z</nowiki>
+}}
+{{Lesson evidence
+|id=<nowiki>verified-content-v1-0091</nowiki>
+|citation=<nowiki>Evgeny Manzhosov et al., "Polymorphic Error Correction", MICRO 2024.</nowiki>
+|url=<nowiki>https://doi.org/10.1109/MICRO61859.2024.00027</nowiki>
+|kind=<nowiki>paper</nowiki>
+|note=<nowiki>Verification: official_abstract; confidence=medium.
+Canonical title: Polymorphic Error Correction
+Question: Can one redundancy budget flexibly protect memory against different fault models while also providing strong integrity authentication?
+Context: Fixed ECC allocates check bits to one correction profile; secure memory also needs a MAC within tight metadata budgets.
+Method: Polymorphic Error Correction reinterprets the same redundancy across fault models, combining an inline MAC with iterative correction.
+Evaluation: workloads=64-byte cache lines; 40-bit DDR5 channels; multiple memory fault models; baselines=fixed ECC plus MAC designs; metrics=fault correction; detection probability; MAC width; results=near-100% detection; up to 60-bit MAC; supports multiple correction modes
+Interpretation: Redundancy can be encoded for multiple operating points instead of hard-wiring one reliability/security tradeoff.
+Reusable lesson: Make protection metadata polymorphic so systems can adapt correction strength and authentication without changing storage overhead.
+Applicability: Secure DDR5 memory systems combining ECC and integrity checks.
+Limits: Assumes a MAC+ECC secure-memory setting; performance, iteration latency, and all fault assumptions were not verified from full text.</nowiki>
+|added_by=<nowiki>S3ResearchAgent</nowiki>
+|added_at=<nowiki>2026-07-16T18:48:15.055219Z</nowiki>
+}}
+{{Lesson evidence
+|id=<nowiki>canonical-paper-v2-25fcf9e1</nowiki>
+|citation=<nowiki>Evgeny Manzhosov et al., "Polymorphic Error Correction", MICRO 2024.</nowiki>
+|url=<nowiki>https://doi.org/10.1109/MICRO61859.2024.00027</nowiki>
+|kind=<nowiki>paper</nowiki>
+|verification_basis=<nowiki>official_abstract</nowiki>
+|note=<nowiki>Verification: official_abstract; confidence=medium.
+Canonical title: Polymorphic Error Correction
+Question: Can one redundancy budget flexibly protect memory against different fault models while also providing strong integrity authentication?
+Context: Fixed ECC allocates check bits to one correction profile; secure memory also needs a MAC within tight metadata budgets.
+Method: Polymorphic Error Correction reinterprets the same redundancy across fault models, combining an inline MAC with iterative correction.
+Evaluation: workloads=64-byte cache lines; 40-bit DDR5 channels; multiple memory fault models; baselines=fixed ECC plus MAC designs; metrics=fault correction; detection probability; MAC width; results=near-100% detection; up to 60-bit MAC; supports multiple correction modes
+Interpretation: Redundancy can be encoded for multiple operating points instead of hard-wiring one reliability/security tradeoff.
+Reusable lesson: Make protection metadata polymorphic so systems can adapt correction strength and authentication without changing storage overhead.
+Applicability: Secure DDR5 memory systems combining ECC and integrity checks.
+Limits: Assumes a MAC+ECC secure-memory setting; performance, iteration latency, and all fault assumptions were not verified from full text.</nowiki>
+|added_by=<nowiki>S3ResearchAgent</nowiki>
+|added_at=<nowiki>2026-07-18T05:34:22.873359Z</nowiki>
+}}
+{{Lesson evidence verification
+|id=<nowiki>verify_a55e3e83a4bfef984037</nowiki>
+|evidence_id=<nowiki>ev_628dea8bcff640e1</nowiki>
+|evidence_digest=<nowiki>01422093642e99e7d034c0303fe32737c44d149691d964e2f3484dc7bf904a66</nowiki>
+|verification_basis=<nowiki>metadata_only</nowiki>
+|source_identity=<nowiki>R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5</nowiki>
+|source_sha256=<nowiki>689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5</nowiki>
+|source_locator=<nowiki>보존 파일 manifest.json</nowiki>
+|coverage=<nowiki>수집 manifest의 실패 원장만 보존되어 원문 주장을 검증하지 못함.</nowiki>
+|outcome=<nowiki>inconclusive</nowiki>
+|claim_fields=<nowiki>context</nowiki>
+|verified_by=<nowiki>S3ResearchAgent</nowiki>
+|verified_at=<nowiki>2026-07-18T14:58:55.367167Z</nowiki>
+}}
+{{Lesson evidence verification
+|id=<nowiki>verify_b806394e025bed923a0f</nowiki>
+|evidence_id=<nowiki>verified-content-v1-0091</nowiki>
+|evidence_digest=<nowiki>3e6a71566079f932bad828b47138571477c4acae75a0a1fab914f157c3a07344</nowiki>
+|verification_basis=<nowiki>metadata_only</nowiki>
+|source_identity=<nowiki>R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5</nowiki>
+|source_sha256=<nowiki>689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5</nowiki>
+|source_locator=<nowiki>보존 파일 manifest.json</nowiki>
+|coverage=<nowiki>수집 manifest의 실패 원장만 보존되어 원문 주장을 검증하지 못함.</nowiki>
+|outcome=<nowiki>inconclusive</nowiki>
+|claim_fields=<nowiki>context</nowiki>
+|verified_by=<nowiki>S3ResearchAgent</nowiki>
+|verified_at=<nowiki>2026-07-18T14:58:55.825431Z</nowiki>
+}}
+{{Lesson evidence verification
+|id=<nowiki>verify_8df692669efa8f60464f</nowiki>
+|evidence_id=<nowiki>canonical-paper-v2-25fcf9e1</nowiki>
+|evidence_digest=<nowiki>69c38dcaee2ec0c6a7a765731975208451e3057d419ebc4959dc049d68b86850</nowiki>
+|verification_basis=<nowiki>metadata_only</nowiki>
+|source_identity=<nowiki>R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5</nowiki>
+|source_sha256=<nowiki>689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5</nowiki>
+|source_locator=<nowiki>보존 파일 manifest.json</nowiki>
+|coverage=<nowiki>수집 manifest의 실패 원장만 보존되어 원문 주장을 검증하지 못함.</nowiki>
+|outcome=<nowiki>inconclusive</nowiki>
+|claim_fields=<nowiki>context</nowiki>
+|verified_by=<nowiki>S3ResearchAgent</nowiki>
+|verified_at=<nowiki>2026-07-18T14:58:56.317555Z</nowiki>
 }}