Hi Ben,
Thanks for the reply.
I will look into this parameters will do the internal testing and let you know
the results.
Regards,
Muneendra.
-Original Message-
From: Benjamin Marzinski [mailto:bmarz...@redhat.com]
Sent: Wednesday, December 21, 2016 9:40 PM
To: Muneendra Kumar M
Hi Ravi,
On Wed, Dec 21, 2016 at 12:38:12PM +, Nalla, Ravikanth wrote:
>
> In dmstats(8) man page, what is the exact difference between "read_time" and
> "read_ticks"
> and also the exact difference between "write_nsecs" and "write_ticks"?
>
> read_time
> Accumulated
Have you looked into the delay_watch_checks and delay_wait_checks
configuration parameters? The idea behind them is to minimize the use
of paths that are intermittently failing.
-Ben
On Mon, Dec 19, 2016 at 11:50:36AM +, Muneendra Kumar M wrote:
>Customers using Linux host (mostly RHEL
On 12/20/2016 10:41 AM, Binoy Jayan wrote:
> At a high level the goal is to maximize the size of data blocks that get
> passed
> to hardware accelerators, minimizing the overhead from setting up and tearing
> down operations in the hardware. Currently dm-crypt itself is a big blocker as
> it
In dmstats(8) man page, what is the exact difference between "read_time" and
"read_ticks"
and also the exact difference between "write_nsecs" and "write_ticks"?
read_time
Accumulated duration of all read requests (ns).
read_ticks
Nanoseconds spent servicing reads.
It seems that this email didn't get delivered due to some stupid gmail
spam policy. Let me try to repost via a different relay. Sorry to those
who have seen the original message and get a duplicate now.
On Wed 21-12-16 08:03:53, Michal Hocko wrote:
> On Tue 20-12-16 14:13:41, Andrew Morton wrote:
