www.icact.org

Member Login

TACT Journal Homepage

Call for Paper

Committee

Find My Paper

Author Homepage

Statistics & History

Welcome Message

Paper Procedure

FAQ

Paper Archives

Outstanding Papers

Program & Proceedings

Presentation Platform

Hotel & Travel Info

Photo Gallery

Scheduler Login

Seminar

Archives Login

Sponsors

Virual Oral Question and Answer


IEEE/ICACT20260320 Question.1 Questioner: wangsy@dsp.ac.cn 2026-02-06 오후 5:25:08	IEEE/ICACT20260320 Answer.1 Answer by Auhor zhaozx@dsp.ac.cn 2026-02-06 오후 5:25:08
How does the refill path of GCCache ensure that each piece of data corresponds exactly to each request? Does it require reordering of the buffer (reorder buffer) or tag matching?	GCCache receives requests from multiple pipelines, each of which is assigned a binary code and corresponds to a fixed Pipeline ID (note: not PID). This Pipeline ID accompanies the entire request processing flow: during the clock cycle for determining whether a request hits the cache, the Pipeline ID is temporarily stored in the Status RAM of the Cache Subsystem. If a request hits the cache, the Cache Subsystem will feed back the Pipeline ID together with the hit result to the Scheduler Subsystem, and its Response Handler module will accurately return the result to the corresponding pipeline based on the Pipeline ID. If a request misses the cache, the Pipeline ID will be stored in the Outstanding Table of the ORP Subsystem; after the host returns the context information, the ORP Subsystem will synchronize the Pipeline ID and context information to the Scheduler Subsystem. Given the small number of pipelines in the peripheral network card, the Pipeline ID occupies a limited number of bits and incurs extremely low RAM resource overhead, so we adopt the design scheme of in-path caching.

Select Voice