| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20101116143149.GC6527@ucw.cz> Date: Tue, 16 Nov 2010 15:31:49 +0100 From: Pavel Machek <pavel@....cz> To: Rogier Wolff <R.E.Wolff@...Wizard.nl> Cc: linux-kernel@...r.kernel.org Subject: Re: Sync semantics. Hi! > What should I expect from a "sync" system call? > > The manual says: > > sync() first commits inodes to buffers, and then buffers to disk. > > and then goes on to state: > > ... since version 1.3.20 Linux does actually wait. > > [for the buffers to be handed over to the drive] > > So how long can I expect a "sync" call to take? > > I would expect that all buffers that are dirty at the time of the > "sync" call are written by the time that sync returns. I'm currently > bombarding my fileserver with some 40-60Mbytes per second of data to > be written (*). The fileserver has 8G of memory. So max 8000 Mb of Are you sure? Hitting 40MB/sec is hard when it involves seeking... You may want to lower dirty_ratio... -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists