On Thu, Apr 14, 2016 at 12:05:40PM -0600, Jason Gunthorpe wrote:
There are some pretty obvious paths to make this saner that could only be a few weeks away, we haven't even had the first conversations yet. I think you are completely wrong there is no 'line of sight' It certainly can't be years.
Does fixing the current write()/writev() problem have any real impact on how we proceed for the "1 char dev to rule them all" idea?
There is some rational for a very driver specific thing, but EEPROM and snoop? Seriously?
That's the thing, I think these are very driver specific [1]. I'm not dead set that the eprom needs to be its own device, it made sense to me, but if others feel the handling should be back in the hfi1 char device I'm fine with that.
As for the snoop stuff, perhaps that would be better in rdmavt? [1] http://marc.info/?l=linux-rdma&m=146065638629146&w=2 -Denny -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
