Date: Tue, 21 Apr 2015 19:46:51 +0000 (UTC) From: LinkedIn Security <security-noreply@linkedin.com> To: Sairam Chengala <freebsd-arch@FreeBSD.org> Subject: Sairam, your password was successfully reset Message-ID: <2026065136.7669603.1429645611348.JavaMail.app@lva1-app8913.prod>
next in thread | raw e-mail | index | archive | help
Hi Sairam, You've successfully changed your LinkedIn password. Thanks for using LinkedIn! The LinkedIn Team When and where this happened: Date:April 21, 2015, 3:46 PM Browser:Chrome Operating System:OS X IP Address:98.109.25.114 Approximate Location:Hoboken, New Jersey, United States Didn't do this? Be sure to change your password right away: https://www.lin= kedin.com/e/v2?e=3Di9hmy-i8rq31nf-4y&a=3Duas-request-password-reset&midToke= n=3DAQFN2Z6JzeYPdA&ek=3Dsecurity_reset_password_notification From owner-freebsd-arch@FreeBSD.ORG Wed Apr 22 02:42:53 2015 Return-Path: <owner-freebsd-arch@FreeBSD.ORG> Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C5AA360F for <freebsd-arch@freebsd.org>; Wed, 22 Apr 2015 02:42:53 +0000 (UTC) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 92EC11E4B for <freebsd-arch@freebsd.org>; Wed, 22 Apr 2015 02:42:53 +0000 (UTC) Received: by igbpi8 with SMTP id pi8so96598973igb.0 for <freebsd-arch@freebsd.org>; Tue, 21 Apr 2015 19:42:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=yhLe4AaieiRv6y25Y4x3zW1RLwIKzDdD0NBEG8EMQIM=; b=aN7efnrKhIDKcmtpH8Sss8PJnFDPR5TApyzdj+SZeG4tkoKsgA/SZq20DF8Kyk9Fyv LRdi33X2VlLiuSJd+C+rsDlU6nwp8ZfMZJHjSrCRY5m6J9BMrvB861mfIAPn+X6bWA6x bhbIbo5+XqmeTIzA9acYUiG8BqmjjswsCOQzhMooSb/z/dlWu0DGs5ue96bD4tm7g1S0 0/CypF0oaqhgE0DjslyyG5rxWdMYBk/K3lp6vISh5YsG0nFwZsrRvilocl4PGk9d78qx SqM1xpuIuA9pXEL75HgV6febjGzJZbHRGciRNHy07GnlcCk2d3H/Fw2mKbuWCIGbdtE9 NNcg== MIME-Version: 1.0 X-Received: by 10.107.46.39 with SMTP id i39mr25407317ioo.8.1429670572562; Tue, 21 Apr 2015 19:42:52 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Tue, 21 Apr 2015 19:42:52 -0700 (PDT) Date: Tue, 21 Apr 2015 19:42:52 -0700 X-Google-Sender-Auth: expZw_WdR1gzF2xocJohes0TJNI Message-ID: <CAJ-VmomL9hZZHPtZ3+TdujHmo5UQfFhm59vQKUbxW++-TGobmg@mail.gmail.com> Subject: RFT: numa policy branch From: Adrian Chadd <adrian@freebsd.org> To: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>, <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>; List-Post: <mailto:freebsd-arch@freebsd.org> List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>, <mailto:freebsd-arch-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 22 Apr 2015 02:42:54 -0000 Hi! I have a branch off of -HEAD that implements the bare minimum for default, per-thread, per-process NUMA allocation policies and associated syscalls / tool to manipulate it. You can all thank Norse for providing me with kit to test this on (including a Dell R910, which is a quad-socket 40-core, 80-thread westmere-EX box with ~1TB of RAM) and time to do the work, and Dell for loaning me way too much hardware to make this happen. It's not ready for formal review for commit (hence why this is a "RFT") but it works well enough in my local test setup that I think it's worth sharing. What it does: * adds VM domain policy and iterator types; * the system default policy is "first-touch-round-robin", which is "first-touch, and if fail, round-robin to other domains"; * there's per-proc and per-thread policy entries in struct proc / struct thread - enough to play with, but certainly not in its final form; * two syscalls - numa_setaffinity() and numa_getaffinity(); * a very basic numactl program, complete with adrian-standard "MAN=". This doesn't teach ULE or the proc/thread stuff anything about NUMA /scheduling/. That's a whole different ballgame. It also has nothing to do with kernel memory allocation - no ULE, no contigmalloc, no driver affinity, etc. This is purely for controlling the initial page allocation for processes - which for a lot of NUMA workloads is all it needs. How to use: * look at the NUMA config file. You have to add in memory domain support or you won't get the domains setup; * sysctl vm.default_domain controls the default policy. "rr", "first-touch-rr" and "first-touch" are supported here. * numactl (--tid=tid or --pid=pid) --policy=policy, --domain=domain, (--get or --set) (optional command) - like cpuset So, some examples: numactl --pid=1 --get Get the current policy for the given PID: # ./numactl --pid=1 --get Policy: none; domain: -1 Run a job with a fixed-domain allocation from domain 1, but pinned to CPU 0 (which on my system is in domain 0, so it's 100% remote memory access): $ cpuset -l 0 ./numactl --policy=fixed-domain --domain=1 ~/himenobmtxpa xl 0 Run a job with round-robin: $ cpuset -l 0 ./numactl --policy=rr ~/himenobmtxpa xl 0 I'm using the 'pcm-numa.x' tool from the intel-pcm package to ensure that memory accesses are correctly local/remote/round-robin as appropriate. I'd appreciate feedback and any improvements (yes, including a manpage) that people have. Thanks! -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2026065136.7669603.1429645611348.JavaMail.app>