On Tue 27-04-10 07:42:49, Dmitry Monakhov wrote: > Jan Kara <jack@xxxxxxx> writes: > > > Provide a function which returns whether a transaction with given tid > > will send a barrier to the filesystem device. The function will be used > > by ext3 to detect whether fsync needs to send a separate barrier or not. > Agree. Except the fact that in case of j_dev != j_fs_dev jbd is still > broken. Yeah, I know about this. I had a look at it but stumbled over a barrier issue in the checkpointing code (http://marc.info/?l=linux-ext4&m=127198235617788&w=2) so I though I'll wait till that gets resolved. > I'm plan to post back-port from jbd2 which makes > journal_trans_will_send_data_barrier() more complex. It have to analyze > commit_transaction->t_flushed_data_blocks. Honza -- Jan Kara <jack@xxxxxxx> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
