All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>,
	"Kenneth Dsouza"
	<kdsouza-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: manpage: update mount.cifs manpage with info about echo_interval option.
Date: Wed, 24 Jan 2018 16:23:03 +0530	[thread overview]
Message-ID: <1516791183.20341.2.camel@redhat.com> (raw)
In-Reply-To: <87y3knsfpa.fsf-IBi9RG/b67k@public.gmane.org>

On Wed, 2018-01-24 at 11:40 +0100, Aurélien Aptel wrote:
> In practice I've noticed that we actually wait for twice the
> echo_interval value to reconnect (/me has been doing a lot of
> reconnection tests lately).
> 
> Cheers,
> 
I've documented it at
http://sprabhu.blogspot.in/2015/08/investigation-into-effects-of-server
.html
if you are interested.

Upstream patch which added this option.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/comm
it/?id=adfeb3e00e8e1b9fb4ad19eb7367e7c272d16003

  parent reply	other threads:[~2018-01-24 10:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 17:37 manpage: update mount.cifs manpage with info about echo_interval option Kenneth Dsouza
     [not found] ` <CAA_-hQJ=DsbeVWU7mr-W0sTRiPXnCC3vznmznQwBedQLtE0s_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-23 23:05   ` Steve French
2018-01-24 10:40   ` Aurélien Aptel
     [not found]     ` <87y3knsfpa.fsf-IBi9RG/b67k@public.gmane.org>
2018-01-24 10:53       ` Sachin Prabhu [this message]
     [not found]         ` <1516791183.20341.2.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-24 11:14           ` Aurélien Aptel
     [not found]             ` <87shavse4a.fsf-IBi9RG/b67k@public.gmane.org>
2018-01-24 12:35               ` Sachin Prabhu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1516791183.20341.2.camel@redhat.com \
    --to=sprabhu-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=aaptel-IBi9RG/b67k@public.gmane.org \
    --cc=kdsouza-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.