Talk:Operating system/Archive 6
![]() | This is an archive of past discussions about Operating system. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | ← | Archive 4 | Archive 5 | Archive 6 |
Software interrupt?
The text A software interrupt (also known as a signal) is a notification to a process that an event has occurred.[1] Whereas a user process can send signals to other user processes and even to itself, signals are usually sent from the kernel.[1]
in #Software interrupt conflicts with Interrupt#Software interrupts. External events such as expiration of time slice, IPC signals and keyboard signals from the user do not fit the definition in Interrupt#Software interrupts, nor have I seen the term applied that way in any OS. Also, there is no text describing how various operating systems handle various types of interrupts.
I propose that the introduction be replaced by the text in Interrupt#Software interrupts and that subsections be added[a] describing sample scenarios in various operating systems. --Shmuel (Seymour J.) Metz Username:Chatul (talk) 11:14, 25 April 2022 (UTC)
- I'm an avid student of how computers work. So, I welcome additional information. However, the Wikipedia rules say secondary research -- reliably sourced. Timhowardriley (talk) 04:01, 1 May 2022 (UTC)
- WP:RS says
secondary sources that present the same material are preferred.
; primary sources are not prohibited. If you know of secondary or tertiary sources covering the same material, please add citations in addition to or in place of the current citations. --Shmuel (Seymour J.) Metz Username:Chatul (talk) 17:12, 1 May 2022 (UTC)- I don't mean to come across as fastidious. But just to be perfectly clear, secondary research is another way of saying not primary (original) research. (I wanted to word the sentence in the positive.) Of course, secondary research may be from primary sources or secondary sources. Timhowardriley (talk) 22:08, 2 May 2022 (UTC)
- WP:RS says
- Regarding "External events such as expiration of time slice, IPC signals and keyboard signals from the user do not fit the definition in Interrupt#Software interrupts": Quoting directly from the textbook: "Among the types of events that cause the kernel to generate a signal for a process are the following: 1) [omitted], 2) [omitted], 3) A software event occurred. For example, input became available on a file descriptor, the terminal window was resized, a timer went off, the process's CPU time limit was exceeded, or a child of this process terminated." The paragraph as written seems kosher. Timhowardriley (talk) 08:25, 1 May 2022 (UTC)
- Interrupt#Software interrupts reads
A software interrupt is requested by the processor itself upon executing particular instructions or when certain conditions are met. Every software interrupt signal is associated with a particular interrupt handler.
; that matches what I have seen elsewhere. The text you quoted does not claim that those events are software interrupts. That citation in no way justifies the existing text. --Shmuel (Seymour J.) Metz Username:Chatul (talk) 17:12, 1 May 2022 (UTC)- The sentence you quoted is uncited. The cited text I quoted does support the existing paragraph in the article. Timhowardriley (talk) 22:19, 2 May 2022 (UTC)
- Interrupt#Software interrupts reads
- I'm an avid student of how computers work. So, I welcome additional information. However, the Wikipedia rules say secondary research -- reliably sourced. Timhowardriley (talk) 04:01, 1 May 2022 (UTC)
Notes
References
- ^ a b Kerrisk, Michael (2010). The Linux Programming Interface. No Starch Press. p. 388. ISBN 978-1-59327-220-3.