Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751902AbWHNGzW (ORCPT ); Mon, 14 Aug 2006 02:55:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751901AbWHNGzV (ORCPT ); Mon, 14 Aug 2006 02:55:21 -0400 Received: from relay.2ka.mipt.ru ([194.85.82.65]:27278 "EHLO 2ka.mipt.ru") by vger.kernel.org with ESMTP id S1751899AbWHNGzT (ORCPT ); Mon, 14 Aug 2006 02:55:19 -0400 Date: Mon, 14 Aug 2006 10:54:55 +0400 From: Evgeniy Polyakov To: Peter Zijlstra Cc: Daniel Phillips , David Miller , linux-mm@kvack.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [RFC][PATCH 0/9] Network receive deadlock prevention for NBD Message-ID: <20060814065454.GA6356@2ka.mipt.ru> References: <1155127040.12225.25.camel@twins> <20060809130752.GA17953@2ka.mipt.ru> <1155130353.12225.53.camel@twins> <20060809.165431.118952392.davem@davemloft.net> <1155189988.12225.100.camel@twins> <44DF888F.1010601@google.com> <20060814051323.GA1335@2ka.mipt.ru> <1155537943.5696.118.camel@twins> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <1155537943.5696.118.camel@twins> User-Agent: Mutt/1.5.9i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.7.5 (2ka.mipt.ru [0.0.0.0]); Mon, 14 Aug 2006 10:54:58 +0400 (MSD) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1434 Lines: 30 On Mon, Aug 14, 2006 at 08:45:43AM +0200, Peter Zijlstra (a.p.zijlstra@chello.nl) wrote: > > Just for clarification - it will be completely impossible to login using > > openssh or some other priveledge separation protocol to the machine due > > to the nature of unix sockets. So you will be unable to manage your > > storage system just because it is in OOM - it is not what is expected > > from reliable system. > > > > > But really, if you expect to run reliable block IO to Zanzibar over an ssh > > > tunnel through a firewall, then you might also consider taking up bungie > > > jumping with the cord tied to your neck. > > > > Just pure openssh for control connection (admin should be able to > > login). > > These periods of degenerated functionality should be short and > infrequent albeit critical for machine recovery. Would you rather have a > slower ssh login (the machine will recover) or drive/fly to Zanzibar to > physically reboot the machine? It will not work, since you can not mark openssh sockets as those which are able to get memory from reserved pool. So admin unable to check the system status and make anything to turn system's life on. -- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/