commit | b1093c6ba21ae3d41946f3a7bb4886b8b90e7c27 | [log] [tgz] |
---|---|---|
author | Willy Tarreau <w@1wt.eu> | Sat Jul 09 18:55:37 2022 +0200 |
committer | Willy Tarreau <w@1wt.eu> | Fri Jul 15 19:43:10 2022 +0200 |
tree | ec8018b076e4ccc3b1a3acf329ab5281cbe79f9d | |
parent | 1b927eb3c35dfdbe73b4852f18e025b8e10e3716 [diff] |
MEDIUM: poller: program the update in fd_update_events() for a migrated FD When an FD is migrated, all pollers program an update. That's useless code duplication, and when thread groups will be supported, this will require an extra round of locking just to verify the update_mask on return. Let's just program the update direction from fd_update_events() as it already does for closed FDs, this becomes more logical.