Welcome, Guest. Please login or register.
Forums
« previous next »
Pages: [1]   Go Down

Author Topic: warp-up specific tools (like copy, etc)  (Read 1078 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: warp-up specific tools (like copy, etc)
« on: October 06, 2005, 11:51:29 AM »
@kas1e

Copy...

No.

And there's a reason for it: Copy spends 99.99% of the time waiting for the I/O subsystem (which is m68k anyway). You gain absolutely nothing from making the copy cmd PPC native. In fact, with WOS it would actually just get slower due to cacheflushing at context switches.
Logged
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: warp-up specific tools (like copy, etc)
« Reply #1 on: October 06, 2005, 12:05:31 PM »
It's not copy that's taking 100% CPU.

For PIO IDE systems the CPU time is mostly spent poking the data to the I/O-register 16-bit as a time, assuming the network is faster than the IDE write speed, that is.
Logged
 
Pages: [1]   Go Up
« previous next »