Re: [bitfolk] VPS still sending packets from 212.13.195.254

Top Page

Reply to this message
Author: Daniel Case
Date:  
Subject: Re: [bitfolk] VPS still sending packets from 212.13.195.254
On 28/05/2012 15:43, Andy Smith wrote:
> Hello,
>
> As you may be aware, BitFolk currently doesn't support 64-bit
> guests. The reasons for this are:
>
> - 64-bit is alleged to be a little slower and use more memory
>    per-process compared to 32-bit.
> - 99.04% of BitFolk customers have less than 2GiB addressable RAM.
> - Supporting only 32-bit or only 64-bit is a bit simpler.

>
> We do, however occasionally lose custom due to not supporting 64-bit
> guests.
>


Another thought to throw in to the mix here is the x32 ABI, introduced
with linux 3.4: this essentially uses all of the architectural features
of x86-64 (thus gaining the benefit of the extra registers and other
improvements over vanilla x86-32), but uses 32-bit addressing. This
gives you much of the benefit of the x86-64 arch without the memory
overhead of 64-bit pointers, and is ideal for circumstances where the
32-bit address space is never going to be exceeded (e.g. the vast
majority of customer VPSes at present). As I understand it (i.e. correct
me if I'm wrong), the kernel itself would still be x86-64, so from a
hosting point of view guests would look & work exactly the same as
regular 64-bit guests.

OS support is some way off yet, for Debian we're probably looking at the
release after Wheezy (i.e. sometime in 2015), by which time the point
may be moot if there is a sufficient abundance of memory. That said,
even with a doubling of RAM I imagine there will still be a decent
proportion of customers with < 2GiB memory at that time for whom an x32
userspace might make sense.

--
Phil



From announce-bounces+users=lists.bitfolk.com@??? Wed May 30 19:09:35 2012
Received: from localhost ([127.0.0.1] helo=bitfolk.com)
    by mail.bitfolk.com with esmtp (Exim 4.72) (envelope-from
    <announce-bounces+users=lists.bitfolk.com@???>)
    id 1SZoH1-0006ZY-9k
    for users@???; Wed, 30 May 2012 19:09:35 +0000
Received: from andy by mail.bitfolk.com with local (Exim 4.72)
    (envelope-from <andy@???>) id 1SZo9x-0006Ld-KO
    for announce@???; Wed, 30 May 2012 19:03:05 +0000
Date: Wed, 30 May 2012 19:02:17 +0000
From: Andy Smith <andy@???>
To: announce@???
Message-ID: <20120530190217.GB11695@???>
MIME-Version: 1.0
OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc
X-URL: http://strugglers.net/wiki/User:Andy
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Wed,
    30 May 2012 19:02:17 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
    spamd0.lon.bitfolk.com
X-Spam-Level: 
X-Spam-ASN: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no
    autolearn=disabled version=3.3.1
X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP
X-BeenThere: announce@???
X-Mailman-Version: 2.1.13
Precedence: list
Content-Type: multipart/mixed; boundary="===============1852312849=="
Sender: announce-bounces+users=lists.bitfolk.com@???
Errors-To: announce-bounces+users=lists.bitfolk.com@lis