diff options
| author | eunhhu <[email protected]> | 2026-09-29 16:13:48 +0100 |
|---|---|---|
| committer | eunhhu <[email protected]> | 2026-09-29 16:13:48 +0100 |
| commit | 500ab6a026c5cb39e04ed74c0cbdf9d482035413 (patch) | |
| tree | 03356a8f9d011800e6ffab6adca51812e2bb4303 /docs/research/048-immutable-read-write-overlap.md | |
| parent | d0be140549b67708039f3c69d0b039440eb3a063 (diff) | |
| download | pure-500ab6a026c5cb39e04ed74c0cbdf9d482035413.tar.gz pure-500ab6a026c5cb39e04ed74c0cbdf9d482035413.zip | |
Put records that come in order straight onto the line, a frame at once
A RECORDS frame of records in order, with nothing held and no record's
tail waiting, went through hold, on_line and line_append a record: the
same checks each time (heard, credit, the line's end, held, the memory
bound). Now they are made once for the frame and its records are copied
onto the line one after another. The receiver's CPU a 61-byte record in
M5 went from 0.15 to 0.133-0.143 us; both sides together 0.28 us, beside
ngtcp2's 0.27 and quinn's 0.31 in the same rounds (the M5 host here also
compares every record with what was sent). test-link's results are the
same to the byte.
Diffstat (limited to 'docs/research/048-immutable-read-write-overlap.md')
0 files changed, 0 insertions, 0 deletions