{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":771959701,"defaultBranch":"dev","name":"operating-system","ownerLogin":"matttbe","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2024-03-14T09:16:18.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/768677?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1710410710.0","currentOid":""},"activityList":{"items":[{"before":"0df9de95ddd77af358192c4e94906b9447257e62","after":"492208ab50fe4573a74b724b91e1a295e3fec5c4","ref":"refs/heads/kernel-mptcp","pushedAt":"2024-03-14T13:05:19.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"matttbe","name":"Matthieu Baerts","path":"/matttbe","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/768677?s=80&v=4"},"commit":{"message":"kernel: enable MPTCP support\n\nThe official description says:\n\n  Multipath TCP (MPTCP) connections send and receive data over multiple\n  subflows in order to utilize multiple network paths. Each subflow uses\n  the TCP protocol, and TCP options carry header information for MPTCP.\n\nThanks to MPTCP, being able to use multiple paths in parallel or\nsimultaneously brings new use-cases:\n\n- Seamless handovers: switching from one path to another while\n  preserving established connections -- Apple is using it for this\n  reason since 2013.\n\n- Best network selection: using the \"best\" available path (latency,\n  losses, cost, bandwidth) -- one path can be used as a \"backup\" one.\n\n- Network aggregation: using multiple paths at the same time to have a\n  higher throughput -- e.g. to combine a fixed an mobile network to\n  send files faster.\n\nFor example, for HA, it is possible to keep a SSH connection alive when\nswitching from one network to another (e.g. while travelling).\n\nTo be able to use MPTCP, both ends need to support it. An application\nhas to request it, by creating an MPTCP socket instead of a TCP one.\nThe rest in unchanged. An alternative is to use 'mptcpize' tool, which\nrelies on LD_PRELOAD to create an MPTCP socket instead of a TCP one.\n\nNote that a MPTCP-enabled server continues to accept regular TCP\nconnections that do not use the Multipath TCP extension without any\nperformance impact. When a connection request is received, and is linked\nto a listening socket with MPTCP support, the kernel will simply check\nif MPTCP options are present. If not, the accepted socket will be a\n\"plain\" TCP one, with the same impact as before.\n\nTo use multiple paths at the same time, additional IP addresses need to\nbe configured, e.g. via the 'ip' tool (IPRoute2).\n\nMPTCP in the kernel is enabled in most main Linux distributions (Debian,\nUbuntu, RedHat, Fedora, etc.), but in more specific ones like Raspbian.\nIt is available in the Linux kernel since v5.6.\n\nSigned-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>","shortMessageHtmlLink":"kernel: enable MPTCP support"}},{"before":"7727bb331de198f1943382e7228e294b3fa4f4f0","after":"0df9de95ddd77af358192c4e94906b9447257e62","ref":"refs/heads/kernel-mptcp","pushedAt":"2024-03-14T10:10:12.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"matttbe","name":"Matthieu Baerts","path":"/matttbe","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/768677?s=80&v=4"},"commit":{"message":"kernel: enable MPTCP support\n\nThe official description says:\n\n  Multipath TCP (MPTCP) connections send and receive data over multiple\n  subflows in order to utilize multiple network paths. Each subflow uses\n  the TCP protocol, and TCP options carry header information for MPTCP.\n\nThanks to MPTCP, being able to use multiple paths in parallel or\nsimultaneously brings new use-cases:\n\n- Seamless handovers: switching from one path to another while\n  preserving established connections -- Apple is using it for this\n  reason since 2013.\n\n- Best network selection: using the \"best\" available path (latency,\n  losses, cost, bandwidth) -- one path can be used as a \"backup\" one.\n\n- Network aggregation: using multiple paths at the same time to have a\n  higher throughput -- e.g. to combine a fixed an mobile network to\n  send files faster.\n\nFor example, for HA, it is possible to keep a SSH connection alive when\nswitching from one network to another (e.g. while travelling).\n\nTo be able to use MPTCP, both ends need to support it. An application\nhas to request it, by creating an MPTCP socket instead of a TCP one.\nThe rest in unchanged. An alternative is to use 'mptcpize' tool, which\nrelies on LD_PRELOAD to create an MPTCP socket instead of a TCP one.\n\nNote that a MPTCP-enabled server continues to accept regular TCP\nconnections that do not use the Multipath TCP extension without any\nperformance impact. When a connection request is received, and is linked\nto a listening socket with MPTCP support, the kernel will simply check\nif MPTCP options are present. If not, the accepted socket will be a\n\"plain\" TCP one, with the same impact as before.\n\nTo use multiple paths at the same time, additional IP addresses need to\nbe configured, e.g. via the 'ip' tool (IPRoute2).\n\nMPTCP in the kernel is enabled in most main Linux distributions (Debian,\nUbuntu, RedHat, Fedora, etc.), but in more specific ones like Raspbian.\nIt is available in the Linux kernel since v5.6.\n\nSigned-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>","shortMessageHtmlLink":"kernel: enable MPTCP support"}},{"before":"5140769c6056edd2f0c8def851e0bdfb9a12d067","after":"7727bb331de198f1943382e7228e294b3fa4f4f0","ref":"refs/heads/kernel-mptcp","pushedAt":"2024-03-14T10:08:42.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"matttbe","name":"Matthieu Baerts","path":"/matttbe","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/768677?s=80&v=4"},"commit":{"message":"kernel: enable MPTCP support\n\nThe official description says:\n\n  Multipath TCP (MPTCP) connections send and receive data over multiple\n  subflows in order to utilize multiple network paths. Each subflow uses\n  the TCP protocol, and TCP options carry header information for MPTCP.\n\nThanks to MPTCP, being able to use multiple paths in parallel or\nsimultaneously brings new use-cases:\n\n- Seamless handovers: switching from one path to another while\n  preserving established connections -- Apple is using it for this\n  reason since 2013.\n\n- Best network selection: using the \"best\" available path (latency,\n  losses, cost, bandwidth) -- one path can be used as a \"backup\" one.\n\n- Network aggregation: using multiple paths at the same time to have a\n  higher throughput -- e.g. to combine a fixed an mobile network to\n  send files faster.\n\nFor example, for HA, it is possible to keep a SSH connection alive when\nswitching from one network to another (e.g. while travelling).\n\nTo be able to use MPTCP, both ends need to support it. An application\nhas to request it, by creating an MPTCP socket instead of a TCP one.\nThe rest in unchanged. An alternative is to use 'mptcpize' tool, which\nuse LD_PRELOAD technique to create an MPTCP socket instead of a TCP one.\n\nNote that a MPTCP-enabled server continues to accept regular TCP\nconnections that do not use the Multipath TCP extension without any\nperformance impact. When a connection request is received, and is linked\nto a listening socket with MPTCP support, the kernel will simply check\nif MPTCP options are present. If not, the accepted socket will be a\n\"plain\" TCP one, with the same impact as before.\n\nTo use multiple paths at the same time, additional IP addresses need to\nbe configured, e.g. via the 'ip' tool (IPRoute2).\n\nMPTCP in the kernel is enabled in most main Linux distributions (Debian,\nUbuntu, RedHat, Fedora, etc.), but in more specific ones like Raspbian.\nIt is available in the Linux kernel since v5.6.\n\nSigned-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>","shortMessageHtmlLink":"kernel: enable MPTCP support"}},{"before":null,"after":"5140769c6056edd2f0c8def851e0bdfb9a12d067","ref":"refs/heads/kernel-mptcp","pushedAt":"2024-03-14T10:05:10.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"matttbe","name":"Matthieu Baerts","path":"/matttbe","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/768677?s=80&v=4"},"commit":{"message":"kernel: enable MPTCP support\n\nThe official description says:\n\n  Multipath TCP (MPTCP) connections send and receive data over multiple\n  subflows in order to utilize multiple network paths. Each subflow uses\n  the TCP protocol, and TCP options carry header information for MPTCP.\n\nThanks to MPTCP, being able to use multiple paths in parallel or\nsimultaneously brings new use-cases:\n\n- Seamless handovers: switching from one path to another while\n  preserving established connections -- Apple is using it for this\n  reason since 2013.\n\n- Best network selection: using the \"best\" available path (latency,\n  losses, cost, bandwidth) -- one path can be used as a \"backup\" one.\n\n- Network aggregation: using multiple paths at the same time to have a\n  higher throughput -- e.g. to combine a fixed an mobile network to\n  send files faster.\n\nFor example, for HA, it is possible to keep a SSH connection alive when\nswitching from one network to another (e.g. while traveling).\n\nTo be able to use MPTCP, both ends need to support it. An application\nhas to request it, by creating an MPTCP socket instead of a TCP one.\nThe rest in unchanged. An alternative is to use 'mptcpize' tool, which\nuse LD_PRELOAD technique to create an MPTCP socket instead of a TCP one.\n\nNote that a MPTCP-enabled server continues to accept regular TCP\nconnections that do not use the Multipath TCP extension without any\nperformance impact. When a connection request is received, and is linked\nto a listening socket with MPTCP support, the kernel will simply check\nif MPTCP options are present. If not, the accepted socket will be a\n\"plain\" TCP one, with the same impact as before.\n\nTo use multiple paths at the same time, additional IP addresses need to\nbe configured, e.g. via the 'ip' tool (IPRoute2).\n\nMPTCP in the kernel is enabled in most main Linux distributions (Debian,\nUbuntu, RedHat, Fedora, etc.), but in more specific ones like Raspbian.\nIt is available in the Linux kernel since v5.6.\n\nSigned-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>","shortMessageHtmlLink":"kernel: enable MPTCP support"}},{"before":"e9ea0995b3d58bb4764329725697c5654e905852","after":null,"ref":"refs/heads/patch-1","pushedAt":"2024-03-14T10:03:31.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"matttbe","name":"Matthieu Baerts","path":"/matttbe","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/768677?s=80&v=4"}},{"before":"c085ff2b104c998e46c9e23716bb55af70840eb5","after":"e9ea0995b3d58bb4764329725697c5654e905852","ref":"refs/heads/patch-1","pushedAt":"2024-03-14T10:01:00.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"matttbe","name":"Matthieu Baerts","path":"/matttbe","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/768677?s=80&v=4"},"commit":{"message":"kernel: enable MPTCP support\n\nThe official description says:\r\n\r\n  Multipath TCP (MPTCP) connections send and receive data over multiple\r\n  subflows in order to utilize multiple network paths. Each subflow uses\r\n  the TCP protocol, and TCP options carry header information for MPTCP.\r\n\r\nThanks to MPTCP, being able to use multiple paths in parallel or\r\nsimultaneously brings new use-cases: \r\n\r\n- Seamless handovers: switching from one path to another while\r\n  preserving established connections -- Apple is using it for this\r\n  reason since 2013.\r\n\r\n- Best network selection: using the \"best\" available path (latency,\r\n  losses, cost, bandwidth) -- one path can be used as a \"backup\" one.\r\n\r\n- Network aggregation: using multiple paths at the same time to have a\r\n  higher throughput -- e.g. to combine a fixed an mobile network to\r\n  send files faster. \r\n\r\nFor example, for HA, it is possible to keep a SSH connection alive when\r\nswitching from one network to another (e.g. while traveling).\r\n\r\nTo be able to use MPTCP, both ends need to support it. An application\r\nhas to request it, by creating an MPTCP socket instead of a TCP one.\r\nThe rest in unchanged. An alternative is to use 'mptcpize' tool, which\r\nuse LD_PRELOAD technique to create an MPTCP socket instead of a TCP one.\r\n\r\nNote that a MPTCP-enabled server continues to accept regular TCP\r\nconnections that do not use the Multipath TCP extension without any\r\nperformance impact. When a connection request is received, and is linked\r\nto a listening socket with MPTCP support, the kernel will simply check\r\nif MPTCP options are present. If not, the accepted socket will be a\r\n\"plain\" TCP one, with the same impact as before.\r\n\r\nTo use multiple paths at the same time, additional IP addresses need to\r\nbe configured, e.g. via the 'ip' tool (IPRoute2).\r\n\r\nMPTCP in the kernel is enabled in most main Linux distributions (Debian,\r\nUbuntu, RedHat, Fedora, etc.), but in more specific ones like Raspbian.\r\nIt is available in the Linux kernel since v5.6.","shortMessageHtmlLink":"kernel: enable MPTCP support"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEFaXi3wA","startCursor":null,"endCursor":null}},"title":"Activity · matttbe/operating-system"}