Jan Kara <jack@xxxxxxx> writes: >> I'd like to know those patches are on what state. Waiting in writeback >> page makes slower, like you mentioned it (I guess it would more >> noticeable if device was slower that like FAT uses). And I think >> currently it doesn't help anything others for blk-integrity stuff >> (without other technic, it doesn't help FS consistency)? >> >> So, why is this locking stuff enabled always? I think it would be better >> to enable only if blk-integrity stuff was enabled. >> >> If it was more sophisticate but more complex stuff (e.g. use >> copy-on-write technic for it), I would agree always enable though. > Well, also software RAID generally needs this feature (so that parity > information / mirror can be properly kept in sync). Not that I'd advocate > that this feature must be always enabled, it's just that there are also > other users besides blk-integrity. I see. So many block layer stuff sounds like broken on corner case? If so, I more feel this approach should be temporary workaround, and should use another less-blocking approach. Thanks. -- OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx> -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>