I added these tickets: 9957 librados: add fadvise op 9958 osd: objectstore: add fadvise op 9959 osd: pass client fadvise hints through to objecstore 9960 osd: adjust hint(s) for replica vs primary writes
I think there are still some open issues, though. For example, let's say the client hints WILLNEED on a replicated pool. Do we put that in the Transaction we apply to the *replicas* too, where we probably want to do DONTNEED (regardless of what the client says)? Does having slightly different transactions for primary vs replica make Transaction encoding problematic? -> Perhaps we put the hint ops in the local_t... Other items: 9956 osd: reenable alloc hints if kernel is known to be safe We need to get to the bottom of the fadvise vs sync_file_range thing. sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
