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

Use kqueue as the backend of AE on DragonFlyBSD #450

Merged
merged 1 commit into from May 12, 2024

Conversation

panjf2000
Copy link
Contributor

@panjf2000 panjf2000 commented May 7, 2024

Currently, we use select(2) on DragonFlyBSD while
kqueue is available on DragonFlyBSD since FreeBSD 4.1
and DragonFlyBSD was originally forked from FreeBSD 4.8

select(2) is a pretty old technique that has many defects
compared to kqueue, we should switch to kqueue on DragonFlyBSD.

Copy link

codecov bot commented May 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.87%. Comparing base (8048abb) to head (24060c9).

Additional details and impacted files
@@             Coverage Diff              @@
##           unstable     #450      +/-   ##
============================================
+ Coverage     69.85%   69.87%   +0.02%     
============================================
  Files           109      109              
  Lines         61791    61791              
============================================
+ Hits          43164    43179      +15     
+ Misses        18627    18612      -15     

see 14 files with indirect coverage changes

src/config.h Show resolved Hide resolved
@panjf2000
Copy link
Contributor Author

@madolson Any updates?

Currently, we use select(2) on DragonFlyBSD while
kqueue is available on DragonFlyBSD since FreeBSD 4.1
and DragonFlyBSD was originally forked from FreeBSD 4.8

select(2) is a pretty old technique that has many defects
compared to kqueue, we should switch to kqueue on DragonFlyBSD.

---------

Signed-off-by: Andy Pan <i@andypan.me>
@madolson madolson merged commit dca1722 into valkey-io:unstable May 12, 2024
17 checks passed
@panjf2000 panjf2000 deleted the kqueue-dragonfly branch May 13, 2024 00:42
adetunjii pushed a commit to adetunjii/valkey that referenced this pull request May 15, 2024
Currently, we use select(2) on DragonFlyBSD while
`kqueue` is available on DragonFlyBSD since FreeBSD 4.1
and DragonFlyBSD was originally forked from FreeBSD 4.8

`select(2)` is a pretty old technique that has many defects
compared to `kqueue`, we should switch to `kqueue` on DragonFlyBSD.

Signed-off-by: Andy Pan <i@andypan.me>
adetunjii pushed a commit to adetunjii/valkey that referenced this pull request May 15, 2024
Currently, we use select(2) on DragonFlyBSD while
`kqueue` is available on DragonFlyBSD since FreeBSD 4.1
and DragonFlyBSD was originally forked from FreeBSD 4.8

`select(2)` is a pretty old technique that has many defects
compared to `kqueue`, we should switch to `kqueue` on DragonFlyBSD.

Signed-off-by: Andy Pan <i@andypan.me>
Signed-off-by: adetunjii <adetunjithomas1@outlook.com>
adetunjii pushed a commit to adetunjii/valkey that referenced this pull request May 15, 2024
Currently, we use select(2) on DragonFlyBSD while
`kqueue` is available on DragonFlyBSD since FreeBSD 4.1
and DragonFlyBSD was originally forked from FreeBSD 4.8

`select(2)` is a pretty old technique that has many defects
compared to `kqueue`, we should switch to `kqueue` on DragonFlyBSD.

Signed-off-by: Andy Pan <i@andypan.me>
Signed-off-by: adetunjii <adetunjithomas1@outlook.com>
hallmason17 pushed a commit to hallmason17/valkey that referenced this pull request May 15, 2024
Currently, we use select(2) on DragonFlyBSD while
`kqueue` is available on DragonFlyBSD since FreeBSD 4.1
and DragonFlyBSD was originally forked from FreeBSD 4.8

`select(2)` is a pretty old technique that has many defects
compared to `kqueue`, we should switch to `kqueue` on DragonFlyBSD.

Signed-off-by: Andy Pan <i@andypan.me>
hallmason17 pushed a commit to hallmason17/valkey that referenced this pull request May 18, 2024
Currently, we use select(2) on DragonFlyBSD while
`kqueue` is available on DragonFlyBSD since FreeBSD 4.1
and DragonFlyBSD was originally forked from FreeBSD 4.8

`select(2)` is a pretty old technique that has many defects
compared to `kqueue`, we should switch to `kqueue` on DragonFlyBSD.

Signed-off-by: Andy Pan <i@andypan.me>
srgsanky pushed a commit to srgsanky/valkey that referenced this pull request May 19, 2024
Currently, we use select(2) on DragonFlyBSD while
`kqueue` is available on DragonFlyBSD since FreeBSD 4.1
and DragonFlyBSD was originally forked from FreeBSD 4.8

`select(2)` is a pretty old technique that has many defects
compared to `kqueue`, we should switch to `kqueue` on DragonFlyBSD.

Signed-off-by: Andy Pan <i@andypan.me>
adetunjii pushed a commit to adetunjii/valkey that referenced this pull request May 22, 2024
Currently, we use select(2) on DragonFlyBSD while
`kqueue` is available on DragonFlyBSD since FreeBSD 4.1
and DragonFlyBSD was originally forked from FreeBSD 4.8

`select(2)` is a pretty old technique that has many defects
compared to `kqueue`, we should switch to `kqueue` on DragonFlyBSD.

Signed-off-by: Andy Pan <i@andypan.me>
Signed-off-by: Samuel Adetunji <adetunjithomas1@outlook.com>
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

Successfully merging this pull request may close these issues.

None yet

2 participants