Tree
- Tree:
4567377ae126b49330504a250ed48e0d957dad24
- Date:
- Message:
- allow Twrite with size bigger than ~16K Until now I've been using a single imsg to handle each messages and the imsg framework has a limit of around 16K for message. For almost all requests, this is fine. Except for Twrite and Tread. This is an attempt to make Twrite handle bigger buffers. The listener process just looks at how big a request is and split it up in multiple messages and the client process tries to remember the fid, position and missing data to continue the write. This means that a single Twrite can be split up in multiple write(2)s.
9pclib.c | commits | blame |
9pclib.h | commits | blame |
kami.h | commits | blame |
log.c | commits | blame |
log.h | commits | blame |
sandbox.c | commits | blame |
sandbox.h | commits | blame |
utils.c | commits | blame |
utils.h | commits | blame |