Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264015AbTFHWhv (ORCPT ); Sun, 8 Jun 2003 18:37:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264023AbTFHWhv (ORCPT ); Sun, 8 Jun 2003 18:37:51 -0400 Received: from hera.cwi.nl ([192.16.191.8]:53156 "EHLO hera.cwi.nl") by vger.kernel.org with ESMTP id S264015AbTFHWht (ORCPT ); Sun, 8 Jun 2003 18:37:49 -0400 From: Andries.Brouwer@cwi.nl Date: Mon, 9 Jun 2003 00:51:23 +0200 (MEST) Message-Id: To: hpa@zytor.com, wli@holomorphy.com Subject: Re: Maximum swap space? Cc: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 737 Lines: 18 The 2GB limit is 100% userspace; distros are already shipping the mkswap(8) fixes (both RH & UL anyway). If I recall things correctly: at some point in time the kernel would reject a swapon on a swapspace that was larger than it could handle (instead of just using the initial part). That is why mkswap contains a lot of very ugly code that compares the size with the maximum certain kernels will accept for swapon. I have not checked recently what the present situation is. Andries - 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/