From: Steve French <smfrench@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Making the in-kernel DNS resolver handle server lists
Date: Wed, 12 Sep 2018 17:27:02 -0500 [thread overview]
Message-ID: <CAH2r5mtVBBDKAeQP0EX-SpBUDVJ_BvHM5kis7rcaD2ZXcZ8x=g@mail.gmail.com> (raw)
In-Reply-To: <28796.1536787099@warthog.procyon.org.uk>
On Wed, Sep 12, 2018 at 4:18 PM David Howells <dhowells@redhat.com> wrote:
>
> Steve French <smfrench@gmail.com> wrote:
>
> > Yes - this could be very useful for cifs (SMB3) in processing DFS
> > (global namespace) referrals and also in Witness protocol
> > redirections, as well as some reconnect scenarios
>
> Would the data format I outlined be sufficient for you?
>
> > (especially when low in memory when upcalls could be risky)
>
> Ummm... It's still upcalling - but a single upcall to fetch a block of
> associated servers and all their addresses.
In a reconnect scenario - anything we can do to make it more likely
reconnect works (especially
with all of the failover, clustering and redirections mechanisms in
SMB3 and later) and can
resolve the new host is good ... so yes even if upcall as long as less
likely to hang ... this
is good
--
Thanks,
Steve
next prev parent reply other threads:[~2018-09-13 3:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 11:11 Making the in-kernel DNS resolver handle server lists David Howells
2018-09-12 20:53 ` Steve French
2018-09-12 21:18 ` David Howells
2018-09-12 22:27 ` Steve French [this message]
2018-09-13 8:38 ` Aurélien Aptel
2018-09-13 18:30 ` Steve French
2018-09-13 9:14 ` David Howells
2018-09-13 20:01 ` David Howells
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='CAH2r5mtVBBDKAeQP0EX-SpBUDVJ_BvHM5kis7rcaD2ZXcZ8x=g@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).