Skip to content
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.

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

DTrace probe gw__write__done is never called. #1576

Closed
leftwo opened this issue Nov 26, 2024 · 1 comment
Closed

DTrace probe gw__write__done is never called. #1576

leftwo opened this issue Nov 26, 2024 · 1 comment

Comments

@leftwo
Copy link
Contributor

leftwo commented Nov 26, 2024

Now that we fast-ack writes (and write_unwritten), we no longer hit the gw__write__done DTrace probe in it's current location.

Figure out if we want something better, or maybe just delete the probe and re-name the current one.

There are a number of dtrace scripts that try to measure things based on the gw__write__done and we should update those to.. do something different.

@leftwo
Copy link
Contributor Author

leftwo commented Jan 29, 2025

Fixed in #1617

the gw__write__done probe is now hit.

@leftwo leftwo closed this as completed Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant