From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 From: lchg Date: Sat, 27 Jan 2018 15:04:28 +0800 Message-ID: To: 9fans@9fans.net Content-Type: multipart/alternative; boundary="94eb2c1cbbc4c3094e0563bc9f6f" Subject: [9fans] Why is the tcp/ip stack of plan9 implemented in kernel? Topicbox-Message-UUID: cb142398-ead9-11e9-9d60-3106f5b1d025 --94eb2c1cbbc4c3094e0563bc9f6f Content-Type: text/plain; charset="UTF-8" In plan9, many os components are moved to user space, even disk file system. But the tcp/ip stack is an exception, what's the consideration for this? Just for performance, or some other reasons? And is there a relatively easy solution to move the stack to user space? --94eb2c1cbbc4c3094e0563bc9f6f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
In plan9, many os components are moved to user spa= ce, even disk file system. But the tcp/ip stack is an exception, what's= the consideration for this? Just for performance, or some other reasons?
And is there a relatively easy solution to move the stack to user space?=

--94eb2c1cbbc4c3094e0563bc9f6f--