➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients nadeem.vawda, neologix, pitrou, ronaldoussoren, santoso.wijaya, sdaoden, vstinner
Date 2011-04-21.21:24:19
SpamBayes Score 0.00033071538
Marked as misclassified No
Message-id <BANLkTin_c2hfwV0Vn+BNGA_2yf=byX-=oQ@mail.gmail.com>
In-reply-to <20110421202659.GA82546@sherwood.local>
Content 
> and it seems - as far as i understand what i read - that you're
> still right; and, furthermore, that fsync() does everything
> anyway.  (But here an idiot is talking about *very* complicated
> stuff.)
>

I just double-checked, and indeed, fsync does flush the disk cache
when barriers are enabled on several FS, while sync_file_range does
not. So sync_file_range should definitely not be used on Linux.
History
Date User Action Args
2011-04-21 21:24:19neologixsetrecipients: + neologix, ronaldoussoren, pitrou, vstinner, nadeem.vawda, santoso.wijaya, sdaoden
2011-04-21 21:24:19neologixlinkissue11877 messages
2011-04-21 21:24:19neologixcreate