On Sat, Aug 01, 2015 at 04:18:31PM -0400, Doug Ledford wrote:
> If you have a legitimate technical reason to NACK this feature, make
> your case. I've publicly stated, in response to Al no less, that I
> don't see justification for making a team re-engineer a working, private
> interface because a disinterested third party finds it "weird". If you
> provide no valid technical justification for your NACK, I'm going to
> disregard it.
It's breaking the semantics that write("foo", len) is the same as writev
of a single vector using writev. We had to add a workaround for the
few broken places doing this which we'd like to remove in the long term.
Note that private driver interface really doesn't matter here.
Everything using file operations does go through the VFS so it does have
major implication on the semantics for all the kernel.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
