On Wed, May 25, 2016 at 08:30:44AM -0400, Jeff Layton wrote: > Maybe it's time to start thinking about how to support multiple layout > types per export? It looks like nobody would want this flex file code in production. The only users will be testers and developers. And the scsi layout is really just a replacement for the block layout, nobody should be supporting both of those at once either. Would it be too much of a burden just to make flexfiles and developers build their own kernels? > It doesn't look like it would be that hard. I think > we could convert ex_layout_type into a bitmap that shows which types > are supported. ex_layout_type is only used internally, the only external interface is an export flag, so we'd need some new interface. --b. > The harder work looks to be on the client. You'd need some heuristic to choose when you get back multiple layout types and fix that to work properly. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
