Talk:Process state

Diagram request[edit]

Hi, as can be seen my MS Paint skills are a little lacking, I'd really like a replacement diagram that shows the same information as the one I (poorly) drew. Thanks in advance. GeorgeBills 08:29, 14 March 2006 (UTC)[reply]

I've removed the request for diagram tag since I see that your request has been filled. Reverie 16:49, 23 March 2006 (UTC)[reply]

A better diagram would include all alternate names for the states (new, ready), in order to match the article text. This could help prevent confusion for the casual reader (which may be what caused the erroneous edit of 19 July 2012‎). -- HLachman (talk) 11:32, 19 September 2012 (UTC)[reply]

Change Virtual Memory to Pagefile?[edit]

The diagram in this article uses outdated terminology. The green region should actually be labeled as "Pagefile" (as named in Windows NT and later) or "Swap space" (as named in Linux). Virtual memory is not the disk space suspended programs are stored in, but actually the concept of virtualizing the address space available to the process and translating the virtual addresses into physical addresses. This means that if a virtual address section were to be added to the diagram, it would cover and include both the yellow and green regions.

This also means that the "Additional process states" section of the article uses outdated terminology. Because different opearting systems use different terms (swapping and paging), I recommend using "sent out" instead of swapped out and "brought in" instead of swapped in. Here's an article to cite on MSDN explaining Windows NT's VM system, which is still in use today: [1]

Basically, I'm just saying this article uses the term Virtual Memory incorrectly and should be changed. Is anyone else out there in agreement with me on this? --198.151.13.10 (talk) 15:58, 18 June 2008 (UTC)[reply]

I agree. However the term "pagefile" is implementation specific I would suggest a more general phase such as "swapped out" or "moved out of main memory". —Preceding unsigned comment added by 118.138.209.199 (talk) 03:27, 7 August 2009 (UTC)[reply]

Done. Royan (talk) 17:01, 15 July 2010 (UTC)[reply]

Suspend?[edit]

What about suspended processes? In Unix you can suspend a foreground process by pressing Control-Z at the terminal, which sends a SIGTSTP to it. It can later be un-suspended with "fg" or "bg" commands. --Spoon! 08:16, 13 March 2007 (UTC)[reply]

This should almost be rewritten anyway, as Stallings' book is a massive pile. DolphinCompSci 21:26, 25 September 2007 (UTC)[reply]

state diagram for process management

Swapped out and blocked[edit]

When would a swapped-out blocked process ever be swapped in until it's no longer blocked? I tagged this with a ^{[citation needed]} tag, although the whole article is unreferenced. Peter Flass (talk) 14:55, 27 April 2014 (UTC)[reply]

OK, I thought of a situation where a process is swapped out while waiting for the expiration of a time interval. I suppose it's possible that the OS would swap it in some time before the interval expires so that it would be ready to run at that time. Peter Flass (talk) 15:08, 28 April 2014 (UTC)[reply]

Waiting state in picture, Ready state in text[edit]

In the picture I see "Waiting", which I think is confusing, as generally on Unix systems I consider the "Waiting" state to be the "Blocked"/"Sleeping"... state.

Then in the text I see "Ready", which is what I would expect.

Suggestion: Use "Ready" everywhere -- — Preceding unsigned comment added by 79.224.210.59 (talk) 13:03, 18 January 2019 (UTC)[reply]