On Fri, Aug 12, 2011 at 04:41:41PM +0200, Jan Schmidt wrote: > After thinking twice, this has a drawback: I'd have to track state > between two read(2) calls, waiting for userspace to "pull" more data. That should be OK. You've got filp->private_data to store your state in, though you'll have to coordinate with btrfs' other use of ->private_data. Not hard, just a little bit of work. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
