ksokk

Perhaps it's time to consider removing the `vmo` mechanism. It seems that this mechanism has poor performance and lacks clear advantages. If the scheduling system continues to rely on this...

> > Perhaps it's time to consider removing the `vmo` mechanism. > > Agree, but we need a proposal for an alternative. > > > If the scheduling system continues...

> > > Perhaps it's time to consider removing the `vmo` mechanism. > > > > > > Agree, but we need a proposal for an alternative. > > Behold,...

``` ~ # ./spawn 1 [ERROR]: Uncaught panic! panicked at /root/asterinas/kernel/aster-nix/src/thread/task.rs:66:10: spawn task failed: NoMemory printing stack trace: 1: fn 0xffffffff890ab960 - pc 0xffffffff890ab978 / registers: rax 0x1; rdx 0xffffffff892bdf60;...

> But I can't see the connection between vfork and inaccurate time. Any more input? vfork() enables the child process to execute prior to the parent process and facilitates more...

> @skpupil Sure, I know what vfork is and why a command like time may use it. I meant the inaccuracy does not seem to have anything do to with...

> > The "user" and "sys" columns seem to display random values. > > I find out the reason. `time` command uses `wait4` syscall to acquire the user time and...


@cchanging I retested the program using the time command, and it took approximately 0.8 seconds. The optimization improvement is significant, and I believe this level of performance is completely acceptable....

>  > > the bug i mentioned in #670 seems not disappear. and The bug ''rhs