Skip to content

Fix ringbuffer ring size reporting #1492

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lmb merged 3 commits into from
Jun 24, 2024
Merged

Fix ringbuffer ring size reporting #1492

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
dcc6137
fix ringbuffer ring size reporting
usamasaqib Jun 20, 2024
346b073
fix test
usamasaqib Jun 21, 2024
66c998d
Update ringbuf/ring.go
florianl Jun 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion ringbuf/ring.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,8 +77,10 @@ func (rr *ringReader) isEmpty() bool {
return prod == cons
}

// The data pages in ring buffers are mapped twice in a single contiguous virtual region
// Therefore the true size is half the size of the mmaped region
func (rr *ringReader) size() int {
return cap(rr.ring)
return cap(rr.ring) / 2
Copy link
Contributor

@brycekahle brycekahle Jun 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you need to fix TestRingbufReader to accommodate this change.

}

// Read a record from an event ring.
Expand Down