Messages in this thread | | | Date | Thu, 8 Jan 2009 14:24:55 +0100 | From | Pavel Machek <> | Subject | Re: 2.6.29 -mm merge plans |
| |
On Wed 2009-01-07 03:57:25, Andi Kleen wrote: > > sys_sync B which is invoked *after* sys_sync caller A should not > > return before A. If you didn't have a global lock, they'd tend to > > block one another's pages anyway. I think it's OK. > > It means that you cannot reboot because reboot does sync. > What happens when the sync gets stuck somewhere on a really > slow device?
And what do you propose? Silently corrupt data on the slow device? -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
| |