[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bfa2159e-1576-6b3c-c85b-ee98bd4f9a47@grimberg.me>
Date: Tue, 25 Jun 2019 15:02:04 -0700
From: Sagi Grimberg <sagi@...mberg.me>
To: Saeed Mahameed <saeedm@...lanox.com>,
"David S. Miller" <davem@...emloft.net>,
Doug Ledford <dledford@...hat.com>,
Jason Gunthorpe <jgg@...lanox.com>
Cc: Leon Romanovsky <leonro@...lanox.com>,
Or Gerlitz <ogerlitz@...lanox.com>,
Tal Gilboa <talgi@...lanox.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
Yamin Friedman <yaminf@...lanox.com>,
Max Gurtovoy <maxg@...lanox.com>
Subject: Re: [for-next V2 08/10] linux/dim: Implement rdma_dim
> +void rdma_dim(struct dim *dim, u64 completions)
> +{
> + struct dim_sample *curr_sample = &dim->measuring_sample;
> + struct dim_stats curr_stats;
> + u32 nevents;
> +
> + dim_update_sample_with_comps(curr_sample->event_ctr + 1,
> + curr_sample->pkt_ctr,
> + curr_sample->byte_ctr,
> + curr_sample->comp_ctr + completions,
> + &dim->measuring_sample);
If this is the only caller, why add pkt_ctr and byte_ctr at all?
Powered by blists - more mailing lists