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.

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

Jump to bottom

need fix for large asynchronous writes. (too big for a single writev call) #1

Closed
y-oda-oni-juba opened this issue Jan 9, 2013 · 3 comments
Closed

need fix for large asynchronous writes. (too big for a single writev call) #1

y-oda-oni-juba opened this issue Jan 9, 2013 · 3 comments
Assignees
@y-oda-oni-juba

Comments

@y-oda-oni-juba
Copy link
Contributor

see frsyuki/mpio#3
@ghost ghost assigned y-oda-oni-juba Jan 10, 2013
y-oda-oni-juba added a commit that referenced this issue Apr 10, 2013
@y-oda-oni-juba
fix event-loop dead-lock on single-large-async write (#1)
a47769b
@y-oda-oni-juba
Copy link
Contributor Author

mpio's event-loop has another issue: new async write event recognition is slow. this makes latency worse.
I will merge https://github.com/aarond10/mpio.git 's linux eventfd based fix. but

  • for compatibility, POSIX pipe based implementation is need
  • delete glog dependency
  • keep mpio::event.next()/more() feature ( these are used by msgpack-rpc C++ )

@kmaehashi
Copy link
Member

Thanks @y-oda-oni-juba, let's raise new issue for that.

@y-oda-oni-juba
Copy link
Contributor Author

I marged this fix to develop branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@y-oda-oni-juba y-oda-oni-juba

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kmaehashi @y-oda-oni-juba