Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:Does it... (Score 1) 199

by paropaco (#20452563) Attached to: The Really Fair Scheduler

Unless, of course, you unlink its executable file, in which case it allocates swap to hold the file first.

Why doesn't it just take into account the fact that the file is in execution in its reference count and leave the file where it is on the file system until it terminates? "unlink" only decrements the reference count, it does not free the file. Seems much simpler to me.

In addition, if it does as you say, FreeBSD does not just need to allocate the swap to hold the file, it actually needs to take every page from the executable file that has not yet been loaded in memory and actually copy it to the swap. Where's the coolness in that?

By the way, I didn't find the paragraph which lead you to that that's how it does in there.

In seeking the unattainable, simplicity only gets in the way. -- Epigrams in Programming, ACM SIGPLAN Sept. 1982

Working...