Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1180487 > unrolled thread
| Started by | Oliver Neukum <oneukum@suse.com> |
|---|---|
| First post | 2015-07-09 09:40 +0200 |
| Last post | 2015-07-09 09:40 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 1/1] suspend: delete sys_sync() Oliver Neukum <oneukum@suse.com> - 2015-07-09 09:40 +0200
| From | Oliver Neukum <oneukum@suse.com> |
|---|---|
| Date | 2015-07-09 09:40 +0200 |
| Subject | Re: [PATCH 1/1] suspend: delete sys_sync() |
| Message-ID | <pKeB3-5JK-15@gated-at.bofh.it> |
On Thu, 2015-07-09 at 00:03 +0200, Rafael J. Wysocki wrote: > Nothing and I'm not discussing that (I've said that already at least once in > this thread). > > What I'm questioning is the "why" of calling sys_sync() from the kernel. That's strictly speaking two questions 1. Why do it in the kernel That is easy. It closes the window of a race condition. 2. Why do it at all In essence because the system becomes inactive. For example we say that data hits the disk after 30s maximum. We cannot meet such a limit unless we sync. There are additional issues, such as a system appearing inactive during suspension and frankly the far greater likelihood of a crash. Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web