> I don't think that would matter. > > Still, I can remove the sync from the suspend code path only, leaving it in > the hibernation code path. The patch will be bigger, but well. > > Any objection to that? Makes sense to sync before suspend tho, to limit the amount of dirty non-written pages in case things go wrong. Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] Remove process freezer from suspend to RAM pathway
- From: "Rafael J. Wysocki" <[email protected]>
- Re: [PATCH] Remove process freezer from suspend to RAM pathway
- References:
- [PATCH] Remove process freezer from suspend to RAM pathway
- From: Matthew Garrett <[email protected]>
- Re: [PATCH] Remove process freezer from suspend to RAM pathway
- From: "Rafael J. Wysocki" <[email protected]>
- Re: [PATCH] Remove process freezer from suspend to RAM pathway
- From: Oliver Neukum <[email protected]>
- Re: [PATCH] Remove process freezer from suspend to RAM pathway
- From: "Rafael J. Wysocki" <[email protected]>
- [PATCH] Remove process freezer from suspend to RAM pathway
- Prev by Date: Re: [PATCH 2/2] net: make net and forcedeth to use kmalloc_node
- Next by Date: [PATCH] Improve behaviour of Dreamcast aica ALSA driver in poor resource conditions
- Previous by thread: Re: [PATCH] Remove process freezer from suspend to RAM pathway
- Next by thread: Re: [PATCH] Remove process freezer from suspend to RAM pathway
- Index(es):
 |