The essence of the dynamic in DIM is that it would fit to the workload running on the cores. For user not to trade bandwidth/cqu% and latency with a module parameter they don't know how to config. If DIM consistently hurts latency of latency critical workloads we should debug and fix. This is where we should go. End goal of no configurate with out of the box performance in terms of both bandwidth/cpu% and latency. We could make several steps towards this direction if we are not mature enough today but let's define them (e.g. tests on different ulps). -----Original Message----- From: linux-rdma-owner@xxxxxxxxxxxxxxx <linux-rdma-owner@xxxxxxxxxxxxxxx> On Behalf Of Sagi Grimberg Sent: Tuesday, July 2, 2019 8:37 AM To: Idan Burstein <idanb@xxxxxxxxxxxx>; Saeed Mahameed <saeedm@xxxxxxxxxxxx>; David S. Miller <davem@xxxxxxxxxxxxx>; Doug Ledford <dledford@xxxxxxxxxx>; Jason Gunthorpe <jgg@xxxxxxxxxxxx> Cc: Leon Romanovsky <leonro@xxxxxxxxxxxx>; Or Gerlitz <ogerlitz@xxxxxxxxxxxx>; Tal Gilboa <talgi@xxxxxxxxxxxx>; netdev@xxxxxxxxxxxxxxx; linux-rdma@xxxxxxxxxxxxxxx; Yamin Friedman <yaminf@xxxxxxxxxxxx>; Max Gurtovoy <maxg@xxxxxxxxxxxx> Subject: Re: [for-next V2 10/10] RDMA/core: Provide RDMA DIM support for ULPs Hey Idan, > " Please don't. This is a bad choice to opt it in by default." > > I disagree here. I'd prefer Linux to have good out of the box experience (e.g. reach 100G in 4K NVMeOF on Intel servers) with the default parameters. Especially since Yamin have shown it is beneficial / not hurting in terms of performance for variety of use cases. The whole concept of DIM is that it adapts to the workload requirements in terms of bandwidth and latency. Well, its a Mellanox device driver after all. But do note that by far, the vast majority of users are not saturating 100G of 4K I/O. The absolute vast majority of users are primarily sensitive to synchronous QD=1 I/O latency, and when the workload is much more dynamic than the synthetic 100%/50%/0% read mix. As much as I'm a fan (IIRC I was the one giving a first pass at this), the dim default opt-in is not only not beneficial, but potentially harmful to the majority of users out-of-the-box experience. Given that this is a fresh code with almost no exposure, and that was not tested outside of Yamin running limited performance testing, I think it would be a mistake to add it as a default opt-in, that can come as an incremental stage. Obviously, I cannot tell what Mellanox should/shouldn't do in its own device driver of course, but I just wanted to emphasize that I think this is a mistake. > Moreover, net-dim is enabled by default, I don't see why RDMA is different. Very different animals.
