From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 3 16:31:37 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DC781065672 for ; Mon, 3 Oct 2011 16:31:37 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 0ED898FC08 for ; Mon, 3 Oct 2011 16:31:36 +0000 (UTC) Received: by qyk10 with SMTP id 10so2483688qyk.13 for ; Mon, 03 Oct 2011 09:31:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Z6F/gmq5yqHsQ/eFTzFzuezMJaEWPMHC8qK1uR3cuN4=; b=gP14QREbKiQReEnJi3jDa83jBD4faxJ5K8+iq2DORVq3qN6ZpyElNA2CmvtESpl5fm fSTWMiFZCcd/cr9l9jUKxAovl+oxa666snr4AaV1WEj4lxhM1xlxC4RFNx3EMn3CcLSS SrYyWel5iaFHGgY7NgJFkD2kiCMbofPEBIDkA= MIME-Version: 1.0 Received: by 10.229.231.149 with SMTP id jq21mr103209qcb.243.1317659496212; Mon, 03 Oct 2011 09:31:36 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.229.83.196 with HTTP; Mon, 3 Oct 2011 09:31:35 -0700 (PDT) In-Reply-To: <1317653757588-4865200.post@n5.nabble.com> References: <1317653757588-4865200.post@n5.nabble.com> Date: Mon, 3 Oct 2011 09:31:35 -0700 X-Google-Sender-Auth: sJfAt-IHII4jBflos18IOOtbsZE Message-ID: From: mdf@FreeBSD.org To: satish kondapalli Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: NUMA Support is there in FreeBSD. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2011 16:31:37 -0000 On Mon, Oct 3, 2011 at 7:55 AM, satish kondapalli wrote: > I am new to FreeBSD, I just want know whether FreeBSD supports NUMA. > If FreeBSD supports NUMA what are the kernel API to allocate memory? > is there any example driver or any driver which is using the NUMA API? > > please provide some inputs... The kernel is NUMA-aware (at least for x86), and memory is allocated round-robin amongst the memory domains. There are not yet any KPIs for allocating memory in a specific NUMA domain, nor for binding specific threads / processes to get their memory local to a bound cpu instead of round robin. There have been several discussions but no one has taken the lead and proposed some KPIs yet. At $WORK the round-robin is sufficient to get consistent performance numbers and we have not yet started any experimentation with binding specific threads to either CPU or memory. Cheers, matthew