Return-Path: Received: from mx3-rdu2.redhat.com ([66.187.233.73]:34534 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726675AbeIMCYm (ORCPT ); Wed, 12 Sep 2018 22:24:42 -0400 From: David Howells In-Reply-To: References: <17451.1536750676@warthog.procyon.org.uk> To: Steve French Cc: dhowells@redhat.com, CIFS , linux-fsdevel Subject: Re: Making the in-kernel DNS resolver handle server lists MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <28795.1536787099.1@warthog.procyon.org.uk> Date: Wed, 12 Sep 2018 22:18:19 +0100 Message-ID: <28796.1536787099@warthog.procyon.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Steve French 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. David