From owner-freebsd-arch@freebsd.org Mon Mar 21 06:12:57 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D400AD6FB1 for ; Mon, 21 Mar 2016 06:12:57 +0000 (UTC) (envelope-from jdani0@leda.lunarmania.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 281AF219 for ; Mon, 21 Mar 2016 06:12:57 +0000 (UTC) (envelope-from jdani0@leda.lunarmania.com) Received: by mailman.ysv.freebsd.org (Postfix) id 275C3AD6FB0; Mon, 21 Mar 2016 06:12:57 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26EACAD6FAF for ; Mon, 21 Mar 2016 06:12:57 +0000 (UTC) (envelope-from jdani0@leda.lunarmania.com) Received: from leda.lunarmania.com (leda.lunarmania.com [67.210.98.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0FFEA218 for ; Mon, 21 Mar 2016 06:12:56 +0000 (UTC) (envelope-from jdani0@leda.lunarmania.com) Received: from jdani0 by leda.lunarmania.com with local (Exim 4.86_1) (envelope-from ) id 1aht54-0004OV-S8 for arch@freebsd.org; Sun, 20 Mar 2016 23:12:46 -0700 To: arch@freebsd.org Subject: ARCH, Notice to appear in Court #000701863 Date: Sun, 20 Mar 2016 23:12:46 -0700 From: "County Court" Reply-To: "County Court" Message-ID: X-Priority: 3 MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - leda.lunarmania.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [32418 32420] / [47 12] X-AntiAbuse: Sender Address Domain - leda.lunarmania.com X-Get-Message-Sender-Via: leda.lunarmania.com: authenticated_id: jdani0/from_h X-Authenticated-Sender: leda.lunarmania.com: jordan.combs@theruckustestteam.com Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2016 06:12:57 -0000 Dear Arch, You have to appear in the Court on the March 29. Please, do not forget to bring all the documents related to the case. Note: The case may be heard by the judge in your absence if you do not come. The Court Notice is attached to this email. Yours faithfully, Jordan Combs, Clerk of Court. From owner-freebsd-arch@freebsd.org Mon Mar 21 22:36:09 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50F52AD83FA for ; Mon, 21 Mar 2016 22:36:09 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3ECD4987 for ; Mon, 21 Mar 2016 22:36:09 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3A76EAD83F9; Mon, 21 Mar 2016 22:36:09 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A154AD83F7 for ; Mon, 21 Mar 2016 22:36:09 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EE120986; Mon, 21 Mar 2016 22:36:08 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id BC45BB9A3; Mon, 21 Mar 2016 18:36:07 -0400 (EDT) From: John Baldwin To: "K. Macy" , "arch@freebsd.org" Subject: Re: Starting APs earlier during boot Date: Mon, 21 Mar 2016 15:34:40 -0700 Message-ID: <4566552.97FFaNSfpg@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <1730061.8Ii36ORVKt@ralph.baldwin.cx> <2980696.6AEyEjetGn@ralph.baldwin.cx> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 21 Mar 2016 18:36:07 -0400 (EDT) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2016 22:36:09 -0000 On Friday, March 18, 2016 12:37:24 PM K. Macy wrote: > So none of these changes have been committed yet? > > I'm hitting hangs in USB on boot with recent HEAD and without having > investigating had thought this might be what exposed the problem. > > Thanks. I've committed some comestic ones (e.g., moving some SYSINITs from SI_SUB_SMP to SI_SUB_LAST), but nothing that should change actual behavior yet. > -M > > On Friday, March 18, 2016, John Baldwin wrote: > > > On Tuesday, February 16, 2016 12:50:22 PM John Baldwin wrote: > > > Currently the kernel bootstraps the non-boot processors fairly early in > > the > > > SI_SUB_CPU SYSINIT. The APs then spin waiting to be "released". We > > currently > > > release the APs as one of the last steps at SI_SUB_SMP. On the one hand > > this > > > removes much of the need for synchronization while SYSINITs are running > > since > > > SYSINITs basically assume they are single-threaded. However, it also > > enforces > > > some odd quirks. Several places that deal with per-CPU resources have to > > > split initialization up so that the BSP init happens in one SYSINIT and > > the > > > initialization of the APs happens in a second SYSINIT at SI_SUB_SMP. > > > > > > Another issue that is becoming more prominent on x86 (and probably will > > also > > > affect other platforms if it isn't already) is that to support working > > > interrupts for interrupt config hooks we bind all interrupts to the BSP > > during > > > boot and only distribute them among other CPUs near the end at > > SI_SUB_SMP. > > > This is especially problematic with drivers for modern hardware > > allocating > > > num(CPUs) interrupts (hoping to use one per CPU). On x86 we have aboug > > 190 > > > IDT vectors available for device interrupts, so in theory we should be > > able to > > > tolerate a lot of drivers doing this (e.g. 60 drivers could allocate 3 > > > interrupts for every CPU and we should still be fine). However, if you > > have, > > > say, 32 cores in a system, then you can only handle about 5 drivers doing > > > this before you run out of vectors on CPU 0. > > > > > > Longer term we would also like to eventually have most drivers attach in > > the > > > same environment during boot as during post-boot. Right now post-boot is > > > quite different as all CPUs are running, interrupts work, etc. One of > > the > > > goals of multipass support for new-bus is to help us get there by probing > > > enough hardware to get timers working and starting the scheduler before > > > probing the rest of the devices. That goal isn't quite realized yet. > > > > > > However, we can run a slightly simpler version of our scheduler before > > > timers are working. In fact, sleep/wakeup work just fine fairly early > > (we > > > allocate the necessary structures at SI_SUB_KMEM which is before the APs > > > are even started). Once idle threads are created and ready we could in > > > theory let the APs startup and run other threads. You just don't have > > working > > > timeouts. OTOH, you can sort of simulate timeouts if you modify the > > scheduler > > > to yield the CPU instead of blocking the thread for a sleep with a > > timeout. > > > The effect would be for threads that do sleeps with a timeout to fall > > back to > > > polling before timers are working. In practice, all of the early kernel > > > threads use sleeps without timeouts when idle so this doesn't really > > matter. > > > > After some more testing, I've simplified the early scheduler a bit. It no > > longer tries to simulate timeouts by just keeping the thread runnable. > > Instead, > > a sleep with a timeout just panics. However, it does still permit sleeps > > with > > infinite sleeps. Some code that uses a timeout really wants a timeout > > (note > > that pause() has a hack to fallback to DELAY() internally if cold is true > > for > > this reason). Instead, my feeling is that any kthreads that need timeouts > > to > > work need to defer their startup until SI_SUB_KICK_SCHEDULER. > > > > > However, I'd like feedback on the general idea and if it is acceptable > > I'd > > > like to coordinate testing with other platforms so this can go into the > > > tree. > > > > I don't think I've seen any objections? This does need more testing. I > > will > > update the patch to add a new EARLY_AP_STARTUP kernel option so this can be > > committed (but not yet enabled) allowing for easier testing (and allowing > > other platforms to catch up to x86). > > > > > The current changes are in the 'ap_startup' branch at > > github/bsdjhb/freebsd. > > > You can view them here: > > > > > > https://github.com/bsdjhb/freebsd/compare/master...bsdjhb:ap_startup > > > > -- > > John Baldwin > > _______________________________________________ > > freebsd-arch@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org > > " > > -- John Baldwin From owner-freebsd-arch@freebsd.org Tue Mar 22 17:45:28 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6475AD8099 for ; Tue, 22 Mar 2016 17:45:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A207D34C for ; Tue, 22 Mar 2016 17:45:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 2EFCCB9AD for ; Tue, 22 Mar 2016 13:45:27 -0400 (EDT) From: John Baldwin To: freebsd-arch@freebsd.org Subject: Re: Wrapper API for static bus_dma allocations Date: Tue, 22 Mar 2016 10:45:19 -0700 Message-ID: <1576055.6UjqO6PkRX@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <2856669.mkVhDvxH7k@ralph.baldwin.cx> References: <2800970.jY4xzTy9Hz@ralph.baldwin.cx> <2856669.mkVhDvxH7k@ralph.baldwin.cx> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 22 Mar 2016 13:45:27 -0400 (EDT) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2016 17:45:28 -0000 On Friday, February 26, 2016 05:10:53 PM John Baldwin wrote: > On Thursday, January 29, 2015 03:37:19 PM John Baldwin wrote: > > The bus_dma API to allocate a chunk of static DMA'able memory (e.g.= for=20 > > descriptor rings) can be a bit obtuse to use in that it require a b= it of=20 > > boilerplate to create a tag, allocate memory for the tag, then load= it to get=20 > > the bus address. Similarly, freeing it also requires several steps= . In=20 > > addition, some of the steps are a bit subtle (e.g. the need to chec= k for an=20 > > error in the bus_dma callback instead of from bus_dmamap_load()) an= d not all=20 > > drivers get those correct. > >=20 > > To try to make this simpler I've written a little wrapper API that = tries to=20 > > provide a single call to allocate a buffer and a single call to fre= e a buffer. =20 > > Each buffer is described by a structure defined by the API, and if = the call to=20 > > allocate a buffer succeeds, the structure contains both a pointer t= o the=20 > > buffer in the kernel's address space as well as a bus address of th= e buffer. > >=20 > > In the interests of simplicity, this API does not allow the buffer = to be quite=20 > > as fully configured as the underlying bus_dma API, instead it aims = to handle=20 > > the most common cases that are used in most drivers. As such, it a= ssumes that=20 > > the buffer must be one contiguous range of DMA address space, and t= he only > > parameters that can be specified are the parent tag, the alignment = of the=20 > > buffer, the lowaddr parameter, the size of the buffer to allocate, = and the=20 > > flags parameter that is normally passed to bus_dmamem_alloc(). I b= elieve that=20 > > this should be sufficient to cover the vast majority of the drivers= in our=20 > > tree. After some more thinking, I've altered this API to include an 'args' st= ruct similar to the one Konstantin used for make_dev_s() to specify constrai= nts. This would permit most constraints to be specified on an as-needed basi= s without requiring all of them each time. It does still assume 1 contig= uous region, but the majority of our drivers require that anyway. I've forward ported this and converted a more typical driver (xl(4)) as= a demo of the new API. You can find the full diff here: https://reviews.freebsd.org/D5704 (I've not yet written manpage updates) Here's the new code in xl(4) to allocate the TX and RX rings. I think = it highlights the specific constraints (alignment, etc.) more clearly than= the previous version: =09=E2=80=8B /* =09=E2=80=8B * Now allocate a chunk of DMA-able memory for the = DMA =09=E2=80=8B * descriptor lists. All of our lists are allocate= d as a =09=E2=80=8B * contiguous block of memory. =09=E2=80=8B */ =09=E2=80=8B bus_dma_mem_args_init(&args); =09=E2=80=8B args.dma_alignment =3D 8; =09=E2=80=8B args.dma_lowaddr =3D BUS_SPACE_MAXADDR_32BIT; =09=E2=80=8B error =3D bus_dma_mem_alloc(bus_get_dma_tag(dev), X= L_RX_LIST_SZ, 0, &args, =09=E2=80=8B &sc->xl_ldata.xl_rx_ring); =09=E2=80=8B if (error) { =09=E2=80=8B device_printf(dev, "failed to allocate rx r= ing\n"); =09=E2=80=8B goto fail; =09=E2=80=8B } =09=E2=80=8B sc->xl_ldata.xl_rx_list =3D sc->xl_ldata.xl_rx_ring= .dma_vaddr; =09=E2=80=8B =09=E2=80=8B error =3D bus_dma_mem_alloc(bus_get_dma_tag(dev), X= L_TX_LIST_SZ, 0, &args, =09=E2=80=8B &sc->xl_ldata.xl_tx_ring); =09=E2=80=8B if (error) { =09=E2=80=8B device_printf(dev, "failed to allocate tx r= ing\n"); =09=E2=80=8B goto fail; =09=E2=80=8B } =09=E2=80=8B sc->xl_ldata.xl_tx_list =3D sc->xl_ldata.xl_tx_ring= .dma_vaddr; =E2=80=8B --=20 John Baldwin From owner-freebsd-arch@freebsd.org Wed Mar 23 00:13:10 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D34499A71A for ; Wed, 23 Mar 2016 00:13:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0D0FF1885 for ; Wed, 23 Mar 2016 00:13:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 088A499A719; Wed, 23 Mar 2016 00:13:10 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0829D99A717 for ; Wed, 23 Mar 2016 00:13:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DF14A1883 for ; Wed, 23 Mar 2016 00:13:09 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4BFF4B953 for ; Tue, 22 Mar 2016 20:13:08 -0400 (EDT) From: John Baldwin To: arch@freebsd.org Subject: More fine-grained NUMA knobs Date: Tue, 22 Mar 2016 17:13:05 -0700 Message-ID: <27035442.YCnG4SQ1mX@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 22 Mar 2016 20:13:08 -0400 (EDT) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2016 00:13:10 -0000 Some of the I/O device affinity stuff such as bus_get_domain() (and the bus_get_cpus() I have in review in D5519) are useful on their own right even if the VM system is not doing NUMA-aware allocations. I think it would be useful to be able to enable these two "prongs" of NUMA awareness independently. To that end, I have a little strawman patch that adds two new kernel options: VM_NUMA_ALLOC and DEVICE_NUMA. I actually think it is probably worth enabling DEVICE_NUMA by default on x86 (and bumping the default MAXMEMDOM to, say, 8 (quad-socket haswell)). You can see the simple patch at: https://github.com/bsdjhb/freebsd/compare/master...bsdjhb:numa_opts Thoughts? -- John Baldwin From owner-freebsd-arch@freebsd.org Wed Mar 23 03:15:17 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A19B1AC9FAF for ; Wed, 23 Mar 2016 03:15:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 856C81D23 for ; Wed, 23 Mar 2016 03:15:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 8118BAC9FAE; Wed, 23 Mar 2016 03:15:17 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80B17AC9FAD for ; Wed, 23 Mar 2016 03:15:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (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 4EB081D21; Wed, 23 Mar 2016 03:15:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x234.google.com with SMTP id o5so12773351iod.2; Tue, 22 Mar 2016 20:15:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=q+YnFBKjrtyKaWhgeSezDEIbnWE8qx4BPbJlDBSu63E=; b=frp32XEBAK0iDNFlS9NjJPWp8vDhUsquAIOcu4EwM+1EHT2hrWhs/wzMjo4ffA1tmO Q2tQzxe8gstKJt/g/3Bag1B4djBc7XUCeYC+3LCH9sB7bTdgaGLY2oV8Z8fv5NWw/imj iELlw9IfR6KkfupBS6/TQGOb2ICInByb426Jv1I/VObN0Ks3Tu77ceNvlKD8MGHLM9oY TYhGBGdtjlo/rohw6oGrYJy1nqf/p8/6lHKbwPFUDM8blZvzqoBDAkpyU6nmc46Iyu5K ldv8iXkn0UC/NfTrTqrUoQtKVrja6P9WnQ+1/mqOTT2afS8UGCTGpBTJw+SyXwoNjsIx DuDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=q+YnFBKjrtyKaWhgeSezDEIbnWE8qx4BPbJlDBSu63E=; b=QensDTFIZ6v9gPMxWb8ytC8PyxwAfOcK6DpJzKlZ6GaVkT8sT/B93MyT0GhdIrAMP/ j1EFp9ASGzEDZ8xAKjam53w4tKo9APrmDNBH+KhE3SStuiUaGm3hQLlog3rtXd4Gc5RM PERsJmQTc438KtZrHnO3Xy6kJIUK62JnW9jvDOk63+EumtVSyyylMOx783cg5uVEos+v Hjv3PGg0v6Xvezsq4O3tTRQyPzw7xBFhwwoU+XGs9BczTC7EGpL7lIrTyx++nB/QfWg8 GCZQuiCeK38cUnSIFZyYM2L566lc4szqX1e1wN9m4e3vyLA5HNmIIPKW7HDE3MVfpzLB rMFw== X-Gm-Message-State: AD7BkJIo77WOzDF7xzvsEEvI/3x6HbdY+JvZZcH+cIF0z67zFhl1tA1e0aKCpiiHBsmcXy6RmeqQOJGAJfBmig== MIME-Version: 1.0 X-Received: by 10.50.8.102 with SMTP id q6mr1046629iga.37.1458702916783; Tue, 22 Mar 2016 20:15:16 -0700 (PDT) Received: by 10.36.14.19 with HTTP; Tue, 22 Mar 2016 20:15:16 -0700 (PDT) In-Reply-To: <27035442.YCnG4SQ1mX@ralph.baldwin.cx> References: <27035442.YCnG4SQ1mX@ralph.baldwin.cx> Date: Tue, 22 Mar 2016 20:15:16 -0700 Message-ID: Subject: Re: More fine-grained NUMA knobs From: Adrian Chadd To: John Baldwin Cc: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2016 03:15:17 -0000 +1 by me! -a On 22 March 2016 at 17:13, John Baldwin wrote: > Some of the I/O device affinity stuff such as bus_get_domain() (and the > bus_get_cpus() I have in review in D5519) are useful on their own right even > if the VM system is not doing NUMA-aware allocations. I think it would be > useful to be able to enable these two "prongs" of NUMA awareness > independently. To that end, I have a little strawman patch that adds two > new kernel options: VM_NUMA_ALLOC and DEVICE_NUMA. I actually think it is > probably worth enabling DEVICE_NUMA by default on x86 (and bumping the > default MAXMEMDOM to, say, 8 (quad-socket haswell)). > > You can see the simple patch at: > > https://github.com/bsdjhb/freebsd/compare/master...bsdjhb:numa_opts > > Thoughts? > > -- > John Baldwin > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" From owner-freebsd-arch@freebsd.org Wed Mar 23 06:39:49 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69FC9AD7CDD for ; Wed, 23 Mar 2016 06:39:49 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 49AE515B2 for ; Wed, 23 Mar 2016 06:39:49 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4911FAD7CDC; Wed, 23 Mar 2016 06:39:49 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48B3FAD7CDA for ; Wed, 23 Mar 2016 06:39:49 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (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 10F0315B0; Wed, 23 Mar 2016 06:39:49 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by mail-vk0-x22b.google.com with SMTP id z68so7473490vkg.3; Tue, 22 Mar 2016 23:39:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=cipQ8YUwyoR+L+NKj44hbbLDnX0nxSWFI4mrMxyWlSc=; b=sVvDmW86VHTFT7hYLJOeln7LrUbX7caPVpREdreXUvLQGVTJVCllaSo7hyrKT0+G+k bHV9//bTLHe0rnKBqZd8C4l7SSOc46hVOI1M/GYyDbSuNQ4un607ovIqJ4Sr07sdCysm rMRFNJA9NuJsG9eFM5pIy9RrdcWykfAQIzhMoX8hsiTRDPmMQoM6GBYFVfhsfbrXfmk5 gCZ8S6+0Sg3zTzvPs1f1eJS7eCDb2iTQsDY2j/oQKCVa/vRJ8MOKzuPD/QkFYX7vnzUd qbNPhm4miNhG6ee9wXI1Pir+OIVY2G56d7ZkaWKiRd36PVmw/vhSqLaDtz85T9UXIFs7 kg8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=cipQ8YUwyoR+L+NKj44hbbLDnX0nxSWFI4mrMxyWlSc=; b=F1/kpnAwhN+g6YfteFzhWhiQCAixz2NYkDxhEu6y/K0E1agbFe5Ld5YEDWOmgQJwVQ NROEtgCPhG/Cuw+fyIV0wHSkOPsOyHr4/ZBLSTQNZJaQ4vyH/aExir7DTJN7az3Y1ivX znxY8P7nmGsnaFDTf/6u5k6rwcB8AI2bOlEq2oiJLEapM+EYq3C/WOp16iNYiC6u/sZv NxpbRPm5oQa02Hl024BA+3usj/KZlxFk/f7/F9PXJlmhXelfSgC3w06Z6FRE0zlfA/Q2 C0I6wUR7yA2eqrd8VyfPENRb3bOvc5AGlZESDYVp7bEfdlsKLL5JbSeT1uFbgAlk8bNM qUqQ== X-Gm-Message-State: AD7BkJKrcu4POfyW+c5juKZIG2F0kcrWB9+gMdyr2ycky65RwUyHNjylP4QZQSOW5zjHIYyo1aEfxjA0fanbvQ== MIME-Version: 1.0 X-Received: by 10.176.0.22 with SMTP id 22mr621289uai.6.1458715188068; Tue, 22 Mar 2016 23:39:48 -0700 (PDT) Received: by 10.31.171.206 with HTTP; Tue, 22 Mar 2016 23:39:48 -0700 (PDT) In-Reply-To: References: <27035442.YCnG4SQ1mX@ralph.baldwin.cx> Date: Tue, 22 Mar 2016 23:39:48 -0700 Message-ID: Subject: Re: More fine-grained NUMA knobs From: Jack Vogel To: Adrian Chadd Cc: John Baldwin , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2016 06:39:49 -0000 Cool! Glad to see this happening :) On Tue, Mar 22, 2016 at 8:15 PM, Adrian Chadd wrote: > +1 by me! > > > -a > > > On 22 March 2016 at 17:13, John Baldwin wrote: > > Some of the I/O device affinity stuff such as bus_get_domain() (and the > > bus_get_cpus() I have in review in D5519) are useful on their own right > even > > if the VM system is not doing NUMA-aware allocations. I think it would > be > > useful to be able to enable these two "prongs" of NUMA awareness > > independently. To that end, I have a little strawman patch that adds two > > new kernel options: VM_NUMA_ALLOC and DEVICE_NUMA. I actually think it > is > > probably worth enabling DEVICE_NUMA by default on x86 (and bumping the > > default MAXMEMDOM to, say, 8 (quad-socket haswell)). > > > > You can see the simple patch at: > > > > https://github.com/bsdjhb/freebsd/compare/master...bsdjhb:numa_opts > > > > Thoughts? > > > > -- > > John Baldwin > > _______________________________________________ > > freebsd-arch@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > From owner-freebsd-arch@freebsd.org Wed Mar 23 07:23:21 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2714AD8632 for ; Wed, 23 Mar 2016 07:23:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 8DEB41993 for ; Wed, 23 Mar 2016 07:23:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 8D4CDAD8631; Wed, 23 Mar 2016 07:23:21 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CF09AD8630 for ; Wed, 23 Mar 2016 07:23:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 289261990; Wed, 23 Mar 2016 07:23:20 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u2N7NGdw056754 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 23 Mar 2016 09:23:16 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u2N7NGdw056754 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u2N7NGl3056753; Wed, 23 Mar 2016 09:23:16 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 23 Mar 2016 09:23:16 +0200 From: Konstantin Belousov To: John Baldwin Cc: arch@freebsd.org Subject: Re: More fine-grained NUMA knobs Message-ID: <20160323072315.GW1741@kib.kiev.ua> References: <27035442.YCnG4SQ1mX@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <27035442.YCnG4SQ1mX@ralph.baldwin.cx> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2016 07:23:21 -0000 On Tue, Mar 22, 2016 at 05:13:05PM -0700, John Baldwin wrote: > Some of the I/O device affinity stuff such as bus_get_domain() (and the > bus_get_cpus() I have in review in D5519) are useful on their own right even > if the VM system is not doing NUMA-aware allocations. I think it would be > useful to be able to enable these two "prongs" of NUMA awareness > independently. To that end, I have a little strawman patch that adds two > new kernel options: VM_NUMA_ALLOC and DEVICE_NUMA. I actually think it is > probably worth enabling DEVICE_NUMA by default on x86 (and bumping the > default MAXMEMDOM to, say, 8 (quad-socket haswell)). > > You can see the simple patch at: > > https://github.com/bsdjhb/freebsd/compare/master...bsdjhb:numa_opts > > Thoughts? I do not like that you check both defined(xxx_NUMA) and MAXMEMDOM > 1. IMO the > 1 part should be dropped. I do not see why would it be useful even as optimization. Otherwise, this looks good. From owner-freebsd-arch@freebsd.org Thu Mar 24 19:37:19 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B12E1ADBD08; Thu, 24 Mar 2016 19:37:19 +0000 (UTC) (envelope-from foxii@bk.ru) Received: from fallback1.mail.ru (fallback1.mail.ru [94.100.181.184]) by mx1.freebsd.org (Postfix) with ESMTP id 5D2F71DED; Thu, 24 Mar 2016 19:37:18 +0000 (UTC) (envelope-from foxii@bk.ru) Received: from f173.i.mail.ru (f173.i.mail.ru [94.100.178.91]) by fallback1.mail.ru (mPOP.Fallback_MX) with ESMTP id 0C9D06C2F738; Thu, 24 Mar 2016 22:06:16 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Type:Message-ID:Reply-To:Date:MIME-Version:Subject:To:From; bh=3UzJU63EH+uaP1oDo7acTLbcz8H/qVao2MDF7qm4jak=; b=XopBwU96ahHiQ2GHlj/9SRpzFEbTvLXsmfJ3u5C2W+aeNbiLTcySkpExi9U63JsR/95EZsZv5MmefFzF59hd3h9XQXYvEol7aRYHD9YelfITK28tMsmd64bA60ugaG5jSkmQxO72aRoGOQPMH9mC8god7E0MeMjFkFLYFLlncyc=; Received: from [31.44.58.133] (ident=mail) by f173.i.mail.ru with local (envelope-from ) id 1ajAa5-0007U5-Qo; Thu, 24 Mar 2016 22:06:06 +0300 Received: from [31.44.58.133] by e.mail.ru with HTTP; Thu, 24 Mar 2016 22:06:05 +0300 From: =?UTF-8?B?0JLQu9Cw0LTQuNC80LjRgA==?= To: freebsd-arch@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-arm@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: =?UTF-8?B?cXVlc3Rpb24gb24gc3VwcG9ydCBwcm9jZXNzb3IgSW50ZWwgQXRvbSBaMzcz?= =?UTF-8?B?NUY=?= MIME-Version: 1.0 X-Mailer: Mail.Ru Mailer 1.0 X-Originating-IP: [31.44.58.133] Date: Thu, 24 Mar 2016 22:06:05 +0300 Reply-To: =?UTF-8?B?0JLQu9Cw0LTQuNC80LjRgA==?= X-Priority: 3 (Normal) Message-ID: <1458846365.574939838@f173.i.mail.ru> X-Mras: Ok X-Spam: undefined Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2016 19:37:19 -0000 IEhlbGxvLCBwbGVhc2UgdGVsbCBtZSB3aGV0aGVyIHRoZSBGcmVlQlNEIG9wZXJhdGluZyBzeXN0 ZW0gSW50ZWwgQXRvbSBaMzczNUY/wqBXaGljaCBkaXN0cmlidXRpb24gSSBuZWVkIHRvIGRvd25s b2FkPwoKCgE= From owner-freebsd-arch@freebsd.org Thu Mar 24 19:39:32 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71B56ADBE36 for ; Thu, 24 Mar 2016 19:39:32 +0000 (UTC) (envelope-from peter.garshtja@ambient-md.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 3B4791F3B for ; Thu, 24 Mar 2016 19:39:32 +0000 (UTC) (envelope-from peter.garshtja@ambient-md.com) Received: by mail-io0-x22a.google.com with SMTP id 124so93889119iov.3 for ; Thu, 24 Mar 2016 12:39:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ambient-md-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=PxNb59yuuJJyNKGn0p/AojQ1579fwx4OQzbT14Ac3KQ=; b=RCbeaFth4MkX2ySwjMkkd+Z7MXtrMwvJTc0e51GjPTgrYghqGSjecU9Bg0oex7Xl0y o3dyEdtjLTn77S0coLjoYqm87LhRq1NrOYYKSagnjMmgsVX8VG854RCs/JLL7q4fFw2a oDAqXiuGrfbifRK3w2Axo1rRH/qu2+dhL0KyTNLlhXoLLSCYFrAFf0MvGBQYStdeLyC0 42yuEroVDjLafTUAjNh1mx72AGPJD8wrRomFFERfyJnQ0WjZSneR89OO5/4L+Ftt7gUv tF4QOi2DmRDboLsH4h0DwKUCf5blt69IrRGQ36Ot/dCKGhZG8rLdzOMBAgxlruqruhnF eBgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=PxNb59yuuJJyNKGn0p/AojQ1579fwx4OQzbT14Ac3KQ=; b=e5Z2c4sC/Cog/J3YS7rqr6DVI//s/h/qxzHYbml2iDkAiNvM+BgT0essF8KJIKhVvh wxbyEA0HDAIuYWM0I1W6pR+fleXBSKyuLAF3dsjaQKKzh+0vxQmTLNL9ov1L8YdfI1pT pUn5tUmD+3Gg3oB66sSO9QQIcu5xGDh5m4Lnp/4iRTlOnStit3mGUs4JJNBKb9/qOPQ7 dXZCfIwzZmWNTDL8bQt9fRcmqxBhmak93VCWXi18pBgD0TtS+YqUII+Pg0QH4BO7boTp EiPuYpu+IR8u8c9oMtJs3fPRn2pNlWofqlCnzac+fpHAyBAIu6XvkKJR/Ip5+8e3UxdR G6RA== X-Gm-Message-State: AD7BkJLIt1Ph0w20NDifsYpHi3cmE/NdsxQXOIOdBiKaNVWVotx8iH4csBg3n3ghCXeuLazJ72+el2hQyy6eyQ== MIME-Version: 1.0 X-Received: by 10.107.14.142 with SMTP id 136mr10155270ioo.94.1458848371145; Thu, 24 Mar 2016 12:39:31 -0700 (PDT) Received: by 10.79.11.71 with HTTP; Thu, 24 Mar 2016 12:39:31 -0700 (PDT) X-Originating-IP: [207.96.192.66] Received: by 10.79.11.71 with HTTP; Thu, 24 Mar 2016 12:39:31 -0700 (PDT) In-Reply-To: <1458846365.574939838@f173.i.mail.ru> References: <1458846365.574939838@f173.i.mail.ru> Date: Thu, 24 Mar 2016 15:39:31 -0400 Message-ID: Subject: Re: question on support processor Intel Atom Z3735F From: peter garshtja To: =?UTF-8?B?0JLQu9Cw0LTQuNC80LjRgA==?= Cc: freebsd-arch@freebsd.org, freebsd-amd64@freebsd.org, freebsd-arm@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2016 19:39:32 -0000 Hi Vladimir, I believe you need x86 arch. Regards On Mar 24, 2016 3:37 PM, "=D0=92=D0=BB=D0=B0=D0=B4=D0=B8=D0=BC=D0=B8=D1=80"= wrote: > Hello, please tell me whether the FreeBSD operating system Intel Atom > Z3735F? Which distribution I need to download? > > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arch@freebsd.org Thu Mar 24 19:46:55 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10855ADC100; Thu, 24 Mar 2016 19:46:55 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id CA38F1439; Thu, 24 Mar 2016 19:46:54 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [127.0.0.1] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id EEBBFF48; Thu, 24 Mar 2016 22:46:50 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Re: question on support processor Intel Atom Z3735F References: <1458846365.574939838@f173.i.mail.ru> To: =?UTF-8?B?0JLQu9Cw0LTQuNC80LjRgA==?= , freebsd-arch@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-arm@FreeBSD.org, freebsd-amd64@FreeBSD.org From: Lev Serebryakov Organization: FreeBSD Message-ID: <56F44422.6050107@FreeBSD.org> Date: Thu, 24 Mar 2016 22:46:42 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <1458846365.574939838@f173.i.mail.ru> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="VsglVVQiJDluXDFjul55pI78WllaStjHE" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2016 19:46:55 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --VsglVVQiJDluXDFjul55pI78WllaStjHE Content-Type: multipart/mixed; boundary="0LAwAIaSmtCVnVFNXgwK8jdJGxPQ1bGj0" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: =?UTF-8?B?0JLQu9Cw0LTQuNC80LjRgA==?= , freebsd-arch@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-arm@FreeBSD.org, freebsd-amd64@FreeBSD.org Message-ID: <56F44422.6050107@FreeBSD.org> Subject: Re: question on support processor Intel Atom Z3735F References: <1458846365.574939838@f173.i.mail.ru> In-Reply-To: <1458846365.574939838@f173.i.mail.ru> --0LAwAIaSmtCVnVFNXgwK8jdJGxPQ1bGj0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 24.03.2016 22:06, =D0=92=D0=BB=D0=B0=D0=B4=D0=B8=D0=BC=D0=B8=D1=80 wro= te: > Intel Atom Z3735F Both x86 (32 bit) and amd64 (64 bit) will do. It depends on available memory. If you have 4GB or more installed, try amd64. --=20 // Lev Serebryakov --0LAwAIaSmtCVnVFNXgwK8jdJGxPQ1bGj0-- --VsglVVQiJDluXDFjul55pI78WllaStjHE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJW9EQoXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePo+wP/0AOjwXT2CTdDLzc9IqK8phs QXkImc/jbP05oDClzORbK3sM1F3bQ7QY2Zs+7YNS6skC6u702dLDNQKtE1rtlujJ Ozkb/tLA7xmZNJ/Id41qp/f39CyD3Sfj77l07zuZxFWVePbYEWlNZT2GxyYeaZ5j AMAr4hr/Wg/MlFUMDd5EvrQSGs84v/EHkn7tlv53wnM+aJsizJEdDQaNgkD9WBdN SFmRXu7kFpCb3v0vskl7A0XLP6kg5WNBcgs4tRkJwSnNfIBzkKR8har8cDl9GJof uTKfMUZDg7sp0jtJCsRuCo0DO7GAFdWOOfo6jkioP+rrB62Jjhxwh79WwJ7iOkxh 9CLohrmWP75PezxAq4gpImlx12msgsQvTzQwYd2GWFd0pZrwRLdQS86owAGXeAC6 BkCOkkl05ljsMMygzXAt3UXXkteqifGduaAtJDBcPnbcvv5VKwOAOyvx26wwB5x/ 83nEc9Hqrimb5O8NJVJ/IZR2gBhNQQ2J6/WSenGHx0oe22ggNVgf5B8haDx/Ak2J NicxV6uykpgVnSc8UBZEJsWiMc4MRgONXefCoPJ3SgwEnvEM49WfE1Vml+tFxXq4 DKm/gyUzHngYgCDeYDkeEWvPtlrXdO3N2tyyp1cb/net4w1NHGHmS4FDMUgW2CxF 8ZHIItrzGRnGaZajKW76 =YGny -----END PGP SIGNATURE----- --VsglVVQiJDluXDFjul55pI78WllaStjHE-- From owner-freebsd-arch@freebsd.org Fri Mar 25 18:17:13 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11191ADD895 for ; Fri, 25 Mar 2016 18:17:13 +0000 (UTC) (envelope-from aminr8860@gmail.com) Received: from mail-vk0-x243.google.com (mail-vk0-x243.google.com [IPv6:2607:f8b0:400c:c05::243]) (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 C2B641371 for ; Fri, 25 Mar 2016 18:17:12 +0000 (UTC) (envelope-from aminr8860@gmail.com) Received: by mail-vk0-x243.google.com with SMTP id a62so8007015vkh.0 for ; Fri, 25 Mar 2016 11:17:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=jfi2netmBm91SwRx6lY+WgoiaDpShfu4jsenGdYOM4U=; b=YCOfd1kynnSTfZR+9y1KfamzzKk0BNx89SaiRLt2469CydHmgLTbpSqDgctxU90OiE CDtuBZgn8rWFzbWglRS3T5qf+3vjcUyWWE0OqIoli7agdBzrc3T67UCbiwxFl52KVyE4 Itl/EKe892T+eb4nFjN3xYfd6WIXrrlGGJpU/ijejwCcO2FcTJyaBoKCmL8/+UTgJlNc 1T1LWOmaxDpjafKjcHCCI6MAIL4jBWsgZUbGmhTCif7AvlGexH/dS6UT2Tyz3NbbyRFg pS2BdV/cNurXTO5/rduJ0sK6K7IZWV56jnxTjSOkwNclui8bHBT6gsoTb1OyIJytP+2I wePg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=jfi2netmBm91SwRx6lY+WgoiaDpShfu4jsenGdYOM4U=; b=awoN2VP0uuS0dlsDXlDlHs5uCd4Qu6P20bL57Fwlj8wgYEQGfGvK5P7/9MG85Ayjw2 lDP0r73JcO59ZZBzUt9c3ZeqBjyN7dpiFmvtdHxkfZw8GaitjA1DJHMZmAJhof194LMN cwbKwhgVHvEeYJ4hRWqbRkwShGQDD0C6zPhM4Q2fVqH9CTy/olzg86yCKoCwB6mUuGVx LLHpHuS44aHPXn9YWQzkWu5Fdsc+P2aM3q55Znd3Ip74ib/SFOru2LXy+ZuDlW1HXiEy iMqbQBMbZxR045T+lgNIPnoHGzj0dIJd2jvUrdgEzZEGAbpLO7KLnlPgqrZ282Fxf5jQ hB+w== X-Gm-Message-State: AD7BkJKmp6hRZ5tDS6cMIZjg3sByzIzh9QfnuRfmJ2TkWS1MYm9x0OY3fJbTrmu4WBP2eDnxT/qTFlNcVQ4Bhg== MIME-Version: 1.0 X-Received: by 10.31.151.75 with SMTP id z72mr7024471vkd.104.1458923366555; Fri, 25 Mar 2016 09:29:26 -0700 (PDT) Received: by 10.176.0.101 with HTTP; Fri, 25 Mar 2016 09:29:26 -0700 (PDT) Received: by 10.176.0.101 with HTTP; Fri, 25 Mar 2016 09:29:26 -0700 (PDT) Date: Fri, 25 Mar 2016 09:29:26 -0700 Message-ID: Subject: Video danludar From: Ruhul amin To: freebsd-arch@FreeBSD.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2016 18:17:13 -0000 aminr8860@gmail.com From owner-freebsd-arch@freebsd.org Fri Mar 25 23:06:57 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8DBBADD05C for ; Fri, 25 Mar 2016 23:06:57 +0000 (UTC) (envelope-from veryfunnyimages@linux102.softhof.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D207F2B62 for ; Fri, 25 Mar 2016 23:06:57 +0000 (UTC) (envelope-from veryfunnyimages@linux102.softhof.net) Received: by mailman.ysv.freebsd.org (Postfix) id CDADDADD05B; Fri, 25 Mar 2016 23:06:57 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD447ADD05A for ; Fri, 25 Mar 2016 23:06:57 +0000 (UTC) (envelope-from veryfunnyimages@linux102.softhof.net) Received: from linux102.softhof.net (static.88-198-25-152.clients.your-server.de [88.198.25.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 93B402B61 for ; Fri, 25 Mar 2016 23:06:56 +0000 (UTC) (envelope-from veryfunnyimages@linux102.softhof.net) Received: from veryfunnyimages by linux102.softhof.net with local (Exim 4.86_1) (envelope-from ) id 1ajZsJ-0039Uy-Aq for arch@freebsd.org; Fri, 25 Mar 2016 23:06:35 +0100 To: arch@freebsd.org Subject: You recieved tax refund payment (case #00000578411) X-PHP-Script: veryfunnyimages.com/post.php for 209.196.192.43 Date: Fri, 25 Mar 2016 22:06:35 +0000 From: "Internal Revenue Service" Reply-To: "Internal Revenue Service" Message-ID: X-Priority: 3 MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - linux102.softhof.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [1159 1170] / [47 12] X-AntiAbuse: Sender Address Domain - linux102.softhof.net X-Get-Message-Sender-Via: linux102.softhof.net: authenticated_id: veryfunnyimages/from_h X-Authenticated-Sender: linux102.softhof.net: office@veryfunnyimages.com Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2016 23:06:58 -0000 You are receiving this notification because your tax refund request has been processed. Please find attached copy of the approved 67570D form you have submitted. Transaction type / Tax Refund Payment method / Wire transfer Amount / $ 2218.00 Status / Processed Form / 67570D Additional information regarding tax refunds can be found on our website: http://www.irs.gov/Refunds. Regards, Internal Revenue Service Address: 1111 Constitution Avenue, NW Washington, DC 20224 Website: http://www.irs.gov Phone: 1-800-829-1040