> >1) Have a simple single fixed input structure for each ioctl. Maybe > >with some extra padding and a flags argument if you think stuff is going > >to be added over time. No generic header. No casting. The ioctl > >number defines the input structure. If you need a different structure > >later, use a different ioctl number. > > -No generic header and No casting- Why not ?
Because it brings no benefits. All the supposed benefits can be achived through careful use of the existing interfaces, ioctl or otherwise. And it has costs: code complexity, run-time cpu/memory, etc. Its benefit/cost ratio is not flattering :). - z -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
