On Mon, Mar 22, 2021 at 03:17:05PM +0000, Rimmer, Todd wrote: > > Over a long time it has been proven that this methodology is a > > good way to effect business change to align with the community > > consensus development model - eventually the costs of being out of > > tree have bad ROI and companies align. > > Agree. The key question is when will nVidia upstream it's drivers > so companies don't have to endure the resulting "bad ROI" of being > forced to have unique out of tree solutions. If you are working with NVIDIA GPU and having inefficiencies then you need to take it through your buisness relationship, not here. > > > Putting a bunch of misaligned structures and random reserved > > > fields *is* garbage by the upstream standard and if I send that > > > to Linus I'll get yelled at. > Let's not overexaggerate this. The fields we're organized in a > logical manner for end user consumption and understanding. A couple > resv fields were used for alignment. No, a couple of resv fields were randomly added and *a lot* of other mis-alignements were ignored. That is not our standard for ABI design. Jason
