Page MenuHomeFreeBSD

kqueue(9): document f_copy
Needs ReviewPublic

Authored by imp on Thu, Nov 20, 4:13 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 23, 11:50 AM
Unknown Object (File)
Fri, Nov 21, 12:58 AM
Unknown Object (File)
Thu, Nov 20, 10:58 PM
Unknown Object (File)
Thu, Nov 20, 10:27 PM
Unknown Object (File)
Thu, Nov 20, 9:01 PM
Unknown Object (File)
Thu, Nov 20, 7:46 PM

Details

Reviewers
kib
Summary

f_copy controls whether and how a knote is inherited by the child
process.

Sponsored by: Netflix

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 68771
Build 65654: arc lint + arc unit

Event Timeline

imp requested review of this revision.Thu, Nov 20, 4:13 PM
pauamma_gundo.com added inline comments.
share/man/man9/kqueue.9
208

Did you mean "knote_triv_copy" here?

share/man/man9/kqueue.9
214

I do not understand the second half of this sentence (WRT error), and think that the first half could be reformulated.
I suggest to say it like this, feel free to edit the language:

Filter might set
.Dv f_copy
to
.Fn knote_triv_copy
if there is no additional resource handling required, besides shallow copying of the knote itself.

update per review...
... hope to get feedback on whether I should mention attach/detach here or not.

In D53845#1231594, @imp wrote:

update per review...
... hope to get feedback on whether I should mention attach/detach here or not.

No, attach/detach are not relevant for copy.

share/man/man9/kqueue.9
200

Why did you dropped the description of the f_copy itself?

Doh! Undrop the actual descirption of f_copy... thanks kib for noticing.

Undrop the description. thanks kib for noticing

share/man/man9/kqueue.9
206

Or maybe "the not will not be copied to the child process"
I'm not sure which is better.

208

yea, I typed it rather than cut and paste.

214

Yes. That's likely better. Do I need to mention anything about errors calling the detach function (which I saw from code inspection)?

share/man/man9/kqueue.9
206

Now I do not quite like either formulation. The idea is to inform that the copied note is not copied. Might be,
When NULL, the current note is not duplicated in the child process kqueue.

share/man/man9/kqueue.9
214

No, there is no need. This is a normal flow for destroying knote, and it does not matter why it happen.