From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 13:46:39 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C1B44CF8; Sun, 21 Sep 2014 13:46:39 +0000 (UTC) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32FCDB9F; Sun, 21 Sep 2014 13:46:39 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id a1so1519073wgh.1 for ; Sun, 21 Sep 2014 06:46:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=dUHZW6u5P42m26QROqHJtcYcfV1ChONfUly2o/A9xNE=; b=G2hSj53NHDzvbi1B+q8p79rklANfRu0cZ4sagBGbkamB3IbAcKwK9WWCl2rSv1rBgr k1BZbzMP/8p6LKOZrcp07T0FqOZJJUpbHxm07GLjU+LLVJF1e9KXHPO4hdaBlKfh2N2o E0apul3Xu1OWiU5VU/DZ/p22RwuaBkLSy2tyoMdPPmQxNQg7NMf+5sB7L2ogrIXHodPR 1AFi43zJwI8yrW+Jh+coqE+Rrd0RTGx7nSqYm/P6flXbqJgOV0db6rb1eVk0l8X1HAcW fHxnVrf25WmvF7dYmNDT6DLsvZGbBCrWUaS1ppMuGsh0qCejm3LgQbzNnT8+TbR6famY q5dg== X-Received: by 10.194.191.135 with SMTP id gy7mr13799877wjc.39.1411307197378; Sun, 21 Sep 2014 06:46:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.179.10 with HTTP; Sun, 21 Sep 2014 06:46:17 -0700 (PDT) In-Reply-To: <541DACA2.3000900@freebsd.org> References: <1411013471.25791.52.camel@jill.exit.com> <541AB164.80707@beastielabs.net> <1411078978.90616.21.camel@jill.exit.com> <541DACA2.3000900@freebsd.org> From: Frank Mayhar Date: Sun, 21 Sep 2014 06:46:17 -0700 Message-ID: Subject: Re: "Invalid partition table" on 10-stable. To: Nathan Whitehorn Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2014 13:46:39 -0000 On Sat, Sep 20, 2014 at 9:34 AM, Nathan Whitehorn wrote: > Could you describe the exact problem here so that we can fix the > installer? If this is the mark one partition active thing, I'm not sure we > can change that, since there are also systems *that* breaks. > I'm not sure I can describe the *exact* problem, since I don't completely understand it. What I can say that if I put the laptop into legacy-boot mode and mark the partition active, it boots. If I put it into UEFI boot mode and install, even if I install the pmbr and mark it active, the BIOS doesn't find it. This is a bit different message from the earlier one I quoted, it's a set of messages clearly from the BIOS claiming that it can't find a boot partition; I can reproduce it and quote it exactly if it would help. It also offers ways to go to Setup, retry the boot or run diagnostics. Marking the partition inactive doesn't help, in fact I couldn't figure out any way to make it detect the partition. In the BIOS, where you choose UEFI, it has a search function. In legacy mode it finds all the possible boot devices, but in UEFI it claims, IIRC, that it can't find an operating system and produces no list of potential boot devices. This is on a Dell Precision M6800, as I said before. If you have any more questions, feel free to ask. -- Frank Mayhar fmayhar@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 14:18:31 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BBE31579; Sun, 21 Sep 2014 14:18:31 +0000 (UTC) Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2CDF6E31; Sun, 21 Sep 2014 14:18:31 +0000 (UTC) Received: by mail-we0-f177.google.com with SMTP id t60so1725171wes.36 for ; Sun, 21 Sep 2014 07:18:29 -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:content-type; bh=JROnMQx5xDoLBZAGuYN5CbPix+EjofZRGYn+concns8=; b=eRGJ1przAaig+zc6mdSn22IMrWuBf4aBTX/ZYFt9smDAkxVMQGde5BiDGtLzBrXaS/ 0vZ1S1y6Xb4dSsIuMkj283U0hy+N5H+iIo6alVg/eu8BgqxqMDOqk5zdknFLX2cES4NL ydjnRMPMfDn4zU4HhvTLpW+Cv9EONdD1jRtICFIHzqvflUFixGK7MGsxmX9BeWJfM49O sIsnyvak8WtVVdLlC+Dj/CT6EEwqlOQ75l5LHw+IgC+YilZxgfcp198OL53b8IfsN9r4 jGfxzzGfjn/B1kFhJI+EwE9nKC1w1U4mJrjHNkxKDu0spg/2fIwkWdUafh2YHvi12ipt UPyA== MIME-Version: 1.0 X-Received: by 10.180.87.161 with SMTP id az1mr9399876wib.13.1411309109156; Sun, 21 Sep 2014 07:18:29 -0700 (PDT) Received: by 10.194.2.71 with HTTP; Sun, 21 Sep 2014 07:18:29 -0700 (PDT) In-Reply-To: References: <1411013471.25791.52.camel@jill.exit.com> <541AB164.80707@beastielabs.net> <1411078978.90616.21.camel@jill.exit.com> <541DACA2.3000900@freebsd.org> Date: Sun, 21 Sep 2014 18:18:29 +0400 Message-ID: Subject: Re: "Invalid partition table" on 10-stable. From: Andrey Fesenko To: Frank Mayhar Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers , Nathan Whitehorn X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2014 14:18:31 -0000 On Sun, Sep 21, 2014 at 5:46 PM, Frank Mayhar wrote: > On Sat, Sep 20, 2014 at 9:34 AM, Nathan Whitehorn > wrote: > >> Could you describe the exact problem here so that we can fix the >> installer? If this is the mark one partition active thing, I'm not sure we >> can change that, since there are also systems *that* breaks. >> > > I'm not sure I can describe the *exact* problem, since I don't completely > understand it. What I can say that if I put the laptop into legacy-boot > mode and mark the partition active, it boots. If I put it into UEFI boot > mode and install, even if I install the pmbr and mark it active, the BIOS > doesn't find it. This is a bit different message from the earlier one I > quoted, it's a set of messages clearly from the BIOS claiming that it can't > find a boot partition; I can reproduce it and quote it exactly if it would > help. It also offers ways to go to Setup, retry the boot or run > diagnostics. Marking the partition inactive doesn't help, in fact I > couldn't figure out any way to make it detect the partition. In the BIOS, > where you choose UEFI, it has a search function. In legacy mode it finds > all the possible boot devices, but in UEFI it claims, IIRC, that it can't > find an operating system and produces no list of potential boot devices. > > This is on a Dell Precision M6800, as I said before. If you have any more > questions, feel free to ask. > -- > Frank Mayhar > fmayhar@gmail.com If I understand correctly, it is a problem of some BIOS laptops. I have Lenovo X220 he also loaded only when partition support in the mbr. GPT table, and have a new EFI boot lead either to not recognize the media, or to reboot without warning. But in this scheme, the notebook is perfectly loaded with ZFS-only system => 63 234441585 ada1 MBR (112G) 63 234441585 1 freebsd [active] (112G) => 0 234441585 ada1s1 BSD (112G) 0 234441585 1 freebsd-zfs (112G) From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 18:22:36 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE8DEB61 for ; Sun, 21 Sep 2014 18:22:36 +0000 (UTC) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 8E9CE85C for ; Sun, 21 Sep 2014 18:22:36 +0000 (UTC) Received: from comporellon.tachypleus.net (polaris.tachypleus.net [75.101.50.44]) (authenticated bits=0) by c.mail.sonic.net (8.14.9/8.14.9) with ESMTP id s8LIMSUX017638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 21 Sep 2014 11:22:29 -0700 Message-ID: <541F1764.2030109@freebsd.org> Date: Sun, 21 Sep 2014 11:22:28 -0700 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: Frank Mayhar Subject: Re: "Invalid partition table" on 10-stable. References: <1411013471.25791.52.camel@jill.exit.com> <541AB164.80707@beastielabs.net> <1411078978.90616.21.camel@jill.exit.com> <541DACA2.3000900@freebsd.org> In-Reply-To: X-Sonic-CAuth: UmFuZG9tSVa8tLLk976bSVneJ4d1mXv+oNKtWh+8Cs0NSL1pV49OYbaQWUXD7BNr5kSKpOmYK47oDzevNbCik6zYJAwSv0xuwFr56jV2xAM= X-Sonic-ID: C;+tdWPrxB5BG8WzZXoK8kYw== M;ep3PPrxB5BG8WzZXoK8kYw== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2014 18:22:36 -0000 On 09/21/14 06:46, Frank Mayhar wrote: > On Sat, Sep 20, 2014 at 9:34 AM, Nathan Whitehorn > > wrote: > > Could you describe the exact problem here so that we can fix the > installer? If this is the mark one partition active thing, I'm not > sure we can change that, since there are also systems *that* breaks. > > > I'm not sure I can describe the *exact* problem, since I don't > completely understand it. What I can say that if I put the laptop > into legacy-boot mode and mark the partition active, it boots. If I > put it into UEFI boot mode and install, even if I install the pmbr and > mark it active, the BIOS doesn't find it. This is a bit different > message from the earlier one I quoted, it's a set of messages clearly > from the BIOS claiming that it can't find a boot partition; I can > reproduce it and quote it exactly if it would help. It also offers > ways to go to Setup, retry the boot or run diagnostics. Marking the > partition inactive doesn't help, in fact I couldn't figure out any way > to make it detect the partition. In the BIOS, where you choose UEFI, > it has a search function. In legacy mode it finds all the possible > boot devices, but in UEFI it claims, IIRC, that it can't find an > operating system and produces no list of potential boot devices. > > This is on a Dell Precision M6800, as I said before. If you have any > more questions, feel free to ask. > -- > Frank Mayhar > fmayhar@gmail.com One more: can you boot the UEFI memstick image in UEFI mode? There's a possible misfeature in the firmware I want to check for. -Nathan From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 19:28:39 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B28E1635 for ; Sun, 21 Sep 2014 19:28:39 +0000 (UTC) Received: from mail-vc0-x229.google.com (mail-vc0-x229.google.com [IPv6:2607:f8b0:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 72E48E18 for ; Sun, 21 Sep 2014 19:28:39 +0000 (UTC) Received: by mail-vc0-f169.google.com with SMTP id id10so2406054vcb.0 for ; Sun, 21 Sep 2014 12:28:38 -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:content-type; bh=dxlh/pe2/2jk6sYjj+MNu5iWOJyplTAqki4VPoy35pM=; b=WUv51uY4UkgBN/k3tt1F3H6/Ja1bTc7Kdu+uZg0IVnCLDYE590NV8LzDqhAV34qLol 3mT4T6G/XdpFMfLOQ993dzm/UkYVlwq3g/iTyMNBnIxTwVM1TwoSg/6y/6TC92qGqTjN LgqZHjKLJMTgOqjGUefPB5lPOEzyDgqnnhmMMH/D/uK0iqYTsjm3hoPfvUSS9oaCjZDB ZrWPRQ/5wLYZ8qo+d7aRYq+yaCEWJherZC/9cwvEko1fJjwvVAZR11GhthcSy8pJ9s06 rktWCaRggTxIH2FBflK+jDGeMUKGVK8M9zrQxZkv/X5qvc0bno0KLgLPAoDCCzxdllK6 eIig== MIME-Version: 1.0 X-Received: by 10.52.53.105 with SMTP id a9mr12833819vdp.5.1411327718390; Sun, 21 Sep 2014 12:28:38 -0700 (PDT) Received: by 10.221.22.130 with HTTP; Sun, 21 Sep 2014 12:28:38 -0700 (PDT) Date: Sun, 21 Sep 2014 15:28:38 -0400 Message-ID: Subject: stack size rlimit From: suresh gumpula To: "freebsd-hackers@freebsd.org" X-Mailman-Approved-At: Sun, 21 Sep 2014 19:40:02 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2014 19:28:39 -0000 Hi, I am experimenting the RLIMIT_INFINITY for RLIMIT_STACK and I observed that we set to maximize(512M) . Looking at kern_setrlimit() , it seems we are checking this condition and reseting to maxssize While reading through the "design and implementation of freebsd" book , I came across a point that we map the shared libraries just below the stack limit. But looking at sample map of curproc, I don't see shared libraries just below the stack limit. in linux , we have two different address map layouts , one is traditional layout which maps shared libraries somewhere in the middle and the other one which maps just below the stack limit. And it seems by default, it prefers the flexible layout. Can somebody please confirm freebsd layout convention. ? This is what I see on freebsd, does not look like its starting below the stack. % cat /proc/curproc/map 0x400000 0x403000 3 0 0xffffff0003711d80 r-x 1 0 0x1000 COW NC vnode /bin/cat NCH -1 0x602000 0x800000 1 0 0xffffff014816aa20 rw- 1 0 0x3000 NCOW NNC default - CH 1002 0x800602000 0x800638000 34 0 0xffffff0003661ca8 r-x 81 40 0x1004 COW NC vnode /libexec/ld-elf.so.1 NCH -1 0x800638000 0x800640000 7 0 0xffffff0147f2ee58 rw- 1 0 0x3000 NCOW NNC default - CH 1002 0x800837000 0x80083b000 4 0 0xffffff0156ec0000 rw- 1 0 0x3000 COW NNC vnode /libexec/ld-elf.so.1 CH 1002 0x80083b000 0x80084a000 5 0 0xffffff0147fa16c0 rw- 1 0 0x3000 NCOW NNC default - CH 1002 0x80084a000 0x800984000 116 0 0xffffff00036156c0 r-x 81 40 0x1004 COW NC vnode /lib/libc.so.7 NCH -1 0x800984000 0x800b84000 0 0 0xffffff0147f32d80 --- 1 0 0x2000 NCOW NNC default - NCH -1 0x800b84000 0x800b8f000 11 0 0xffffff0147fb7510 rw- 1 0 0x3000 COW NNC vnode /lib/libc.so.7 CH 1002 0x800b8f000 0x800bf4000 4 0 0xffffff01481676c0 rw- 2 0 0x3000 NCOW NNC default - CH 1002 0x800c00000 0x800e00000 4 0 0xffffff01481676c0 rw- 2 0 0x3000 NCOW NNC default - CH 1002 0x7ffffffe0000 0x800000000000 3 0 0xffffff0156e09000 rwx 1 0 0x3000 NCOW NNC default - CH 1002 Thanks Suresh From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 19:59:49 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1A04EB67 for ; Sun, 21 Sep 2014 19:59:49 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 95084FE for ; Sun, 21 Sep 2014 19:59:48 +0000 (UTC) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id s8LJxh22045017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Sep 2014 22:59:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua s8LJxh22045017 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id s8LJxhdk045016; Sun, 21 Sep 2014 22:59:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 21 Sep 2014 22:59:43 +0300 From: Konstantin Belousov To: suresh gumpula Subject: Re: stack size rlimit Message-ID: <20140921195943.GK2210@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nEsDIrWrg+hrB7l1" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2014 19:59:49 -0000 --nEsDIrWrg+hrB7l1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 21, 2014 at 03:28:38PM -0400, suresh gumpula wrote: > Hi, > I am experimenting the RLIMIT_INFINITY for RLIMIT_STACK and I observed > that we set to maximize(512M) . > Looking at kern_setrlimit() , it seems we are checking this condition and > reseting to maxssize >=20 > While reading through the "design and implementation of freebsd" book , I > came across a point that we map the shared libraries just below the stack > limit. But looking at sample map of curproc, I don't see shared libraries > just below the stack limit. >=20 > in linux , we have two different address map layouts , one is traditional > layout which maps shared libraries somewhere in the middle and the other > one which maps just below the stack limit. > And it seems by default, it prefers the flexible layout. >=20 > Can somebody please confirm freebsd layout convention. ? > This is what I see on freebsd, does not look like its starting below the > stack. The default mmap() area starts right after the end of the max data fragment. I.e., it is after the data segment of the main binary + RLIMIT_DATA. The runtime linker and kernel image activator (for the interpreter mapping) utilize default mmap() selection of the address. You can see this in your map below. >=20 > % cat /proc/curproc/map > 0x400000 0x403000 3 0 0xffffff0003711d80 r-x 1 0 0x1000 COW NC vnode > /bin/cat NCH -1 > 0x602000 0x800000 1 0 0xffffff014816aa20 rw- 1 0 0x3000 NCOW NNC default - > CH 1002 > 0x800602000 0x800638000 34 0 0xffffff0003661ca8 r-x 81 40 0x1004 COW NC > vnode /libexec/ld-elf.so.1 NCH -1 > 0x800638000 0x800640000 7 0 0xffffff0147f2ee58 rw- 1 0 0x3000 NCOW NNC > default - CH 1002 > 0x800837000 0x80083b000 4 0 0xffffff0156ec0000 rw- 1 0 0x3000 COW NNC vno= de > /libexec/ld-elf.so.1 CH 1002 > 0x80083b000 0x80084a000 5 0 0xffffff0147fa16c0 rw- 1 0 0x3000 NCOW NNC > default - CH 1002 > 0x80084a000 0x800984000 116 0 0xffffff00036156c0 r-x 81 40 0x1004 COW NC > vnode /lib/libc.so.7 NCH -1 > 0x800984000 0x800b84000 0 0 0xffffff0147f32d80 --- 1 0 0x2000 NCOW NNC > default - NCH -1 > 0x800b84000 0x800b8f000 11 0 0xffffff0147fb7510 rw- 1 0 0x3000 COW NNC > vnode /lib/libc.so.7 CH 1002 > 0x800b8f000 0x800bf4000 4 0 0xffffff01481676c0 rw- 2 0 0x3000 NCOW NNC > default - CH 1002 > 0x800c00000 0x800e00000 4 0 0xffffff01481676c0 rw- 2 0 0x3000 NCOW NNC > default - CH 1002 > 0x7ffffffe0000 0x800000000000 3 0 0xffffff0156e09000 rwx 1 0 0x3000 NCOW > NNC default - CH 1002 --nEsDIrWrg+hrB7l1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUHy4vAAoJEJDCuSvBvK1BcEYP/iWGThVZWXBuifB5WDl/NuR9 ykIx/+1mPXPXnULhEK0d21rBAh34Ay0Jog8+XXrgszomPv2c1WfRtxmgvH0b1HBU j32BKjfJmAxkY6iFUp9MN5Zb2NqvlJT93/qMS+XBxzC7kTOQBMWvanqHwz5Hw/y0 Ge/lMp7fQ5a9+ErzN/yytGW+4k1zmmUwlBsHUaZunTa/m/Tqi+nuUfGOxjDCK3um e43QXqCXywwo7UnNcwIrKl6CvyOFZWGG50/3suSu1UNtqlHoHgSabK4KPHLP5FFj f1iM7hP8hqkCJv7VudKyxOZIiNhki2t+GQ2/tOJMTv1qMv3ZipWm2sm1K8Ojr/Tw S2DQL4zBXkwiawkcSk5ZXDfecrSOhVnz3VIM8ab8UZjdESSuAeO4eSkQ5DBg4ox7 NCFhgz2mTWkhZdIrkIClo1UOM6RQ1jHMsNe8mp6vI1Uo/FJh2/Y+l/HafJUAbvnq opUYZj9h4swExiauWbHZHXbqUtT/j4oyJm3dGSVu9xNaQmtSs8Dd7O5B/qN6saly mb3UedFVyXlynMCWCsca1kYVyooMkYx0y9rW37IwPTIBy8ctb3cQIJtMBoBzfmDG pucPo79OQ+FgP0jxgN33CbJEMJowhyC9DbX+YSCfe0uS67n3opLWHklXhzOcfv5B inhuM0Xp/nIqw5jWIT3I =CzS0 -----END PGP SIGNATURE----- --nEsDIrWrg+hrB7l1-- From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 20:04:07 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 92E34CA8 for ; Sun, 21 Sep 2014 20:04:07 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 028B31B1 for ; Sun, 21 Sep 2014 20:04:06 +0000 (UTC) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id s8LK41hF046148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Sep 2014 23:04:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua s8LK41hF046148 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id s8LK41XT046147; Sun, 21 Sep 2014 23:04:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 21 Sep 2014 23:04:01 +0300 From: Konstantin Belousov To: btw@mail.ustc.edu.cn Subject: Re: What's the difference between kmem_arena and kernel_arena? Message-ID: <20140921200401.GL2210@kib.kiev.ua> References: <1473289.768021411196850376.JavaMail.coremail@mailweb> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ibvzjYYg+QDzMCy1" Content-Disposition: inline In-Reply-To: <1473289.768021411196850376.JavaMail.coremail@mailweb> User-Agent: Mutt/1.5.23 (2014-03-12) 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.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2014 20:04:07 -0000 --ibvzjYYg+QDzMCy1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 20, 2014 at 03:07:30PM +0800, btw@mail.ustc.edu.cn wrote: > Hi All, >=20 > There are two similar variables declared in vm/vm_kern.h, they are kernel= _arena > and kmem_arena. Both of them are used in kmem_malloc(): >=20 > rv =3D kmem_back((vmem =3D=3D kmem_arena) ? kmem_object : kernel_= object, >=20 > I'm wondering what's the difference between them. Why both of them are ne= eded? > I have done a lot of searching, but I still can not find an answer. Look at their usage. kmem_arena is used for the kernel malloc() and page-sized uma allocations. kernel_arena is used by miscellaneous other kernel needs, e.g. for kernel stacks of threads, as the backing for kva_alloc() etc. --ibvzjYYg+QDzMCy1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUHy8wAAoJEJDCuSvBvK1Bt98P/234wuuVkI7vVi/ah/Zsa+lb 8DBhRZ+9gBOZ75NRXN+PUO3mpRJch3xl61+AVO0B7B5Uqr79bQOHEffZ4oTXRUjB t7+6Ib9xB6VoOLflq5cEvRHvgZtbdaRACiSI6fGvMFlqSJa8rSG9L4ygUAWFMPz1 1N00qTe2GxWJsHhedJF6GWe2DZDdZ9IRgGOiQqW+ptThcozM7D6Q2OReHyebdTei Ea2ZNLXRIVYPzQ9YhgOnkbWLGW2mNVbMTSByqdsEBgUS9PfPlgz0VHAvh0MBy/b9 E0YUBztXKLu3h+HuKx98aDe8lwAgVA7R9aVxLyAFEfaL1g1ToSYrNqLyKlWDa5CX jhlUak3dopusF7UzDFkjPgagdnrfQY1ae4sID5HziU6QqAbYVWVoGJqtN5EhMFQn qulrBAam11yCNpx+WPSb2EbAy9YZ4azmOMOa88zWHtNQ/LJ5GPu0DdpmKElHxQUX /lip40XrcX0224Dguy7+eRFqpgl9/0v3onI6xxP0TstMtNYbWhTeMcd1emiyS/lo 56QnXR+fe40/5KCDJjy1dgQOvBl2YidgbEshFdhm74ZuPAXJepMNe/KgQ1zCCB54 OkUxU20DgMJblE+of/6zlSA15BeORwd8g9x/4DsJ1MKInmtNCnoOuBrR+u0t9BpF qY4ud/lKdzYb3DFlmb7L =iwRC -----END PGP SIGNATURE----- --ibvzjYYg+QDzMCy1-- From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 20:19:39 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4ED20E16 for ; Sun, 21 Sep 2014 20:19:39 +0000 (UTC) Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [IPv6:2607:f8b0:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C2D429F for ; Sun, 21 Sep 2014 20:19:38 +0000 (UTC) Received: by mail-vc0-f180.google.com with SMTP id hq11so3494051vcb.11 for ; Sun, 21 Sep 2014 13:19:38 -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:content-type; bh=FeQqNFd69Pf2z4RfkwtKTPWT576N3iHabnoOwuzNcCo=; b=CcKIIf+gRg9TfZ6+xkvBVK/le36BXgCANPNPcRqCFxjxwMk2teuoOQZe7Z94P/9Op/ vhVBEzYL5ZbrKntwPf+XhJnCS/nG+rmkRnBMWvtbCvMbEbEJuDVXusSFgam7ZEcUJrDf O+B1+zKlUcxrslPRZMQpjfKQtEcmjZuZ4WA9RyeJ0jRU54gdJkuO97/C3qCEsHmFU4pk dXRGvbD2h1RIF+We7y6LxzwwphaYomCpNbhiX/SURJnPzhAfyDvGKZL+/vm/MTItfcPq FP4ti/VUanM6HvuZFpKHnj7v9vWKszSdotW4IGNM+VQdaYb+PdgAX7Ar2MV0fMvU2hhA lxtQ== MIME-Version: 1.0 X-Received: by 10.52.35.105 with SMTP id g9mr2550087vdj.61.1411330778174; Sun, 21 Sep 2014 13:19:38 -0700 (PDT) Received: by 10.221.22.130 with HTTP; Sun, 21 Sep 2014 13:19:38 -0700 (PDT) In-Reply-To: <20140921195943.GK2210@kib.kiev.ua> References: <20140921195943.GK2210@kib.kiev.ua> Date: Sun, 21 Sep 2014 16:19:38 -0400 Message-ID: Subject: Re: stack size rlimit From: suresh gumpula To: Konstantin Belousov X-Mailman-Approved-At: Sun, 21 Sep 2014 20:28:03 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2014 20:19:39 -0000 Thank you ! . So we cannot have the stack size beyond 512M . correct ? % sudo ./test_stack Current limit value is : 8M max limit value is : 512M Changing the limits to infinity... Current limit value now is : 512M max limit value now is : 512M Thanks Suresh On Sun, Sep 21, 2014 at 3:59 PM, Konstantin Belousov wrote: > On Sun, Sep 21, 2014 at 03:28:38PM -0400, suresh gumpula wrote: > > Hi, > > I am experimenting the RLIMIT_INFINITY for RLIMIT_STACK and I > observed > > that we set to maximize(512M) . > > Looking at kern_setrlimit() , it seems we are checking this condition > and > > reseting to maxssize > > > > While reading through the "design and implementation of freebsd" book , I > > came across a point that we map the shared libraries just below the stack > > limit. But looking at sample map of curproc, I don't see shared > libraries > > just below the stack limit. > > > > in linux , we have two different address map layouts , one is > traditional > > layout which maps shared libraries somewhere in the middle and the other > > one which maps just below the stack limit. > > And it seems by default, it prefers the flexible layout. > > > > Can somebody please confirm freebsd layout convention. ? > > This is what I see on freebsd, does not look like its starting below the > > stack. > > The default mmap() area starts right after the end of the max data > fragment. I.e., it is after the data segment of the main binary + > RLIMIT_DATA. > > The runtime linker and kernel image activator (for the interpreter > mapping) utilize default mmap() selection of the address. > > You can see this in your map below. > > > > % cat /proc/curproc/map > > 0x400000 0x403000 3 0 0xffffff0003711d80 r-x 1 0 0x1000 COW NC vnode > > /bin/cat NCH -1 > > 0x602000 0x800000 1 0 0xffffff014816aa20 rw- 1 0 0x3000 NCOW NNC default > - > > CH 1002 > > 0x800602000 0x800638000 34 0 0xffffff0003661ca8 r-x 81 40 0x1004 COW NC > > vnode /libexec/ld-elf.so.1 NCH -1 > > 0x800638000 0x800640000 7 0 0xffffff0147f2ee58 rw- 1 0 0x3000 NCOW NNC > > default - CH 1002 > > 0x800837000 0x80083b000 4 0 0xffffff0156ec0000 rw- 1 0 0x3000 COW NNC > vnode > > /libexec/ld-elf.so.1 CH 1002 > > 0x80083b000 0x80084a000 5 0 0xffffff0147fa16c0 rw- 1 0 0x3000 NCOW NNC > > default - CH 1002 > > 0x80084a000 0x800984000 116 0 0xffffff00036156c0 r-x 81 40 0x1004 COW NC > > vnode /lib/libc.so.7 NCH -1 > > 0x800984000 0x800b84000 0 0 0xffffff0147f32d80 --- 1 0 0x2000 NCOW NNC > > default - NCH -1 > > 0x800b84000 0x800b8f000 11 0 0xffffff0147fb7510 rw- 1 0 0x3000 COW NNC > > vnode /lib/libc.so.7 CH 1002 > > 0x800b8f000 0x800bf4000 4 0 0xffffff01481676c0 rw- 2 0 0x3000 NCOW NNC > > default - CH 1002 > > 0x800c00000 0x800e00000 4 0 0xffffff01481676c0 rw- 2 0 0x3000 NCOW NNC > > default - CH 1002 > > 0x7ffffffe0000 0x800000000000 3 0 0xffffff0156e09000 rwx 1 0 0x3000 NCOW > > NNC default - CH 1002 > From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 20:34:16 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 49E9D2DA for ; Sun, 21 Sep 2014 20:34:16 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 ACEA3605 for ; Sun, 21 Sep 2014 20:34:15 +0000 (UTC) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id s8LKYBvq053032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Sep 2014 23:34:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua s8LKYBvq053032 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id s8LKYAP6053031; Sun, 21 Sep 2014 23:34:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 21 Sep 2014 23:34:10 +0300 From: Konstantin Belousov To: suresh gumpula Subject: Re: stack size rlimit Message-ID: <20140921203410.GM2210@kib.kiev.ua> References: <20140921195943.GK2210@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x1F0m3RQhDZyj8sd" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2014 20:34:16 -0000 --x1F0m3RQhDZyj8sd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 21, 2014 at 04:19:38PM -0400, suresh gumpula wrote: > Thank you ! . So we cannot have the stack size beyond 512M . correct ? You have to adjust kern.maxssiz to be able to bump RLIMIT_STACK beyond 512M (on amd64). Just curious, why do you need this ? >=20 > % sudo ./test_stack > Current limit value is : 8M > max limit value is : 512M >=20 > Changing the limits to infinity... >=20 > Current limit value now is : 512M > max limit value now is : 512M --x1F0m3RQhDZyj8sd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUHzZCAAoJEJDCuSvBvK1BblIQAJccX3woINySDZl96SaJDyMN sJShqVxracOL1o6Jjg+xHsaEtbM7vguZav/eEm5IS0GZ7SOCLqvY+nDhsY0TzsvX Jhv80LGIGSILvgik4oS6jsNWFA5jri9mdGHz4ry+w8E+TEOkpqoirmA0iuwBBTap bTG75CObc80E5NMUU8cVq/lA6Mg8a9oQAaGk2Nk27lxElwmfS5uDw8SS4T1R4caH 16b2bs9b9x42R3u+y1aFKBPjuXpwaJTmbHOjzdbP5L9uroA3gQCUsWmDpE3riNt7 wwCy5ow/T+NoKHtSf+dpuDIMyKsq3fMnuPtwsjC/04Uc6lNpfkTAIEQzTPIBl2ay 2iTouGhQY4xB6PuSoBfxdeomt/1hH1Zl3nB9AVrYTvywCTxPGQAcakE4kohz6M+w jgkLqadkqZ7UQDq/SEMaEM9gAg4biPGfksjNvM3PABcfshnqahpVr6vLJOMYtNtz 5chVypOL16sx8kKy5TsjnL9/zjciaNzKhyGa16PnwvIsf9SFrw5T0usGrTxVA33M n+6bIfqkdCK1/UATp8g4fx8nqanr+FEzdj5GBmpgyxmp3AaZiMvOhoUgnvH+PyuK Nla+DAud2BCul/e4iOTG4JIxkT4sZIggRwEEkKX3k/M+SD2m0Lsq78deUBYK31KO ShDmbtOKV9IxUY8NMJCI =mGcK -----END PGP SIGNATURE----- --x1F0m3RQhDZyj8sd-- From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 20:43:52 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D18D777 for ; Sun, 21 Sep 2014 20:43:52 +0000 (UTC) Received: from mail-vc0-x22d.google.com (mail-vc0-x22d.google.com [IPv6:2607:f8b0:400c:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49AE36EE for ; Sun, 21 Sep 2014 20:43:52 +0000 (UTC) Received: by mail-vc0-f173.google.com with SMTP id le20so3615564vcb.32 for ; Sun, 21 Sep 2014 13:43:51 -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:content-type; bh=/ZCPVC5m6TI+H/Wxi+DWL2toL9qfIZDl2CMjYhOVAtg=; b=refif8tfSNW45CtrGj+0oF+SbMNjuhzyoSKCr6y4ah6kZWYuIY7FG+5QhU2Kxt0YG/ 3ACu11MMO5KqFc7BhfMmQhMUeN5/E7I3HHfYKGYc1gs99hHaAmR8IeAGGwlk7j54FlOh IbWvluj8UByI2YLU0+3Kb/D3xUvFvtV9Dj9N7nKLI1j/9ajWqsvYPJZZBeCSTjNC724n xtFHPvzdwbeVLpaqsqjlIj6ieX6eXmVRzf9tJy5ip4iv7gNRlc1RjanALYGEGLp9Jv+1 18B5Rk4hOBP/iYrAh5YsDi8RJsv6GU/xb8Z0tkfLM8kNB3AFtPgsk5Bth5ibr5o1R+Be daIA== MIME-Version: 1.0 X-Received: by 10.220.251.200 with SMTP id mt8mr7497133vcb.24.1411332231198; Sun, 21 Sep 2014 13:43:51 -0700 (PDT) Received: by 10.221.22.130 with HTTP; Sun, 21 Sep 2014 13:43:51 -0700 (PDT) In-Reply-To: <20140921203410.GM2210@kib.kiev.ua> References: <20140921195943.GK2210@kib.kiev.ua> <20140921203410.GM2210@kib.kiev.ua> Date: Sun, 21 Sep 2014 16:43:51 -0400 Message-ID: Subject: Re: stack size rlimit From: suresh gumpula To: Konstantin Belousov X-Mailman-Approved-At: Sun, 21 Sep 2014 21:09:38 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2014 20:43:52 -0000 Yes, we may not really need this big stack space for a process. I am just experimenting RLIMIT_INFINITY on BSD and linux. On BSD we are limiting to kern.maxssiz it seems. And the address map layout which described in the design book , is not what we are doing as you said. Thank you! On Sun, Sep 21, 2014 at 4:34 PM, Konstantin Belousov wrote: > On Sun, Sep 21, 2014 at 04:19:38PM -0400, suresh gumpula wrote: > > Thank you ! . So we cannot have the stack size beyond 512M . correct ? > You have to adjust kern.maxssiz to be able to bump RLIMIT_STACK beyond > 512M (on amd64). > > Just curious, why do you need this ? > > > > > % sudo ./test_stack > > Current limit value is : 8M > > max limit value is : 512M > > > > Changing the limits to infinity... > > > > Current limit value now is : 512M > > max limit value now is : 512M > From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 03:19:11 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C5474B2E for ; Mon, 22 Sep 2014 03:19:11 +0000 (UTC) Received: from ustc.edu.cn (email6.ustc.edu.cn [IPv6:2001:da8:d800::8]) by mx1.freebsd.org (Postfix) with ESMTP id 8856DE88 for ; Mon, 22 Sep 2014 03:19:09 +0000 (UTC) Received: from btw ( [58.211.218.74] ) by ajax-webmail-mailweb (Coremail) ; Mon, 22 Sep 2014 11:19:05 +0800 (CST) Date: Mon, 22 Sep 2014 11:19:05 +0800 (CST) From: btw@mail.ustc.edu.cn To: "Konstantin Belousov" Message-ID: <5002061.890581411355945170.JavaMail.coremail@mailweb> In-Reply-To: <20140921200401.GL2210@kib.kiev.ua> References: <20140921200401.GL2210@kib.kiev.ua> <1473289.768021411196850376.JavaMail.coremail@mailweb> Subject: Re: Re: What's the difference between kmem_arena and kernel_arena? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Originating-IP: [58.211.218.74] X-Priority: 3 X-Mailer: Coremail Webmail Server Version XT_U3b build 111111(15684.4153.3993) Copyright (c) 2002-2014 www.mailtech.cn ustc-xl X-CM-TRANSID: yia_0ZDLcQEplR9UAKJKBA--.26007W X-CM-SenderInfo: xewzqzxdloh3xvwfhvlgxou0/1tbiAQUPAUqSOCfPMQACsx X-Coremail-Antispam: 1U50xBIdaVrnn0S07vEb7Iv0xC_Cr1lV2xY67kC6x804xJvcS sGvfC2KfnxnUU== Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2014 03:19:11 -0000 I got it! Thank you so much! ;-) -twb > -----Original E-mail----- > From: "Konstantin Belousov" > Sent Time: 2014-9-22 4:04:01 > To: btw@mail.ustc.edu.cn > Cc: freebsd-hackers@freebsd.org > Subject: Re: What's the difference between kmem_arena and kernel_arena? > > On Sat, Sep 20, 2014 at 03:07:30PM +0800, btw@mail.ustc.edu.cn wrote: > > Hi All, > > > > There are two similar variables declared in vm/vm_kern.h, they are kernel_arena > > and kmem_arena. Both of them are used in kmem_malloc(): > > > > rv = kmem_back((vmem == kmem_arena) ? kmem_object : kernel_object, > > > > I'm wondering what's the difference between them. Why both of them are needed? > > I have done a lot of searching, but I still can not find an answer. > > Look at their usage. > > kmem_arena is used for the kernel malloc() and page-sized uma allocations. > kernel_arena is used by miscellaneous other kernel needs, e.g. for > kernel stacks of threads, as the backing for kva_alloc() etc. From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 20:36:12 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5A725F6B; Mon, 22 Sep 2014 20:36:12 +0000 (UTC) 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 307A2383; Mon, 22 Sep 2014 20:36:12 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 43AA8B946; Mon, 22 Sep 2014 16:36:11 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: 9.1 callout behavior Date: Mon, 22 Sep 2014 16:07:16 -0400 Message-ID: <3348399.yonqFcmVBb@ralph.baldwin.cx> User-Agent: KMail/4.10.5 (FreeBSD/10.0-STABLE; KDE/4.10.5; amd64; ; ) In-Reply-To: References: <52A731FD.8060307@FreeBSD.org> 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, 22 Sep 2014 16:36:11 -0400 (EDT) Cc: Bret Ketchum , Adrian Chadd , Alexander Motin X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2014 20:36:12 -0000 On Tuesday, September 16, 2014 04:17:20 PM Adrian Chadd wrote: > Hi! > > I know this is bringing up an old thread, but Dell has shipped us some > hardware (thanks Dell!) and I'm helping them take a look at it. > > On 10 December 2013 07:23, Alexander Motin wrote: > > On 10.12.2013 17:12, Bret Ketchum wrote: > >> Do either of you have a dual socket/package motherboard to play > >> > >> with? I've tried a couple single socket motherboards and cannot > >> reproduce the issue. I'm wondering if this occurs on only multi-socket > >> mobos. > > > > My main test system is dual-socket (Supermicro X8DTU). > > It's reasonably reproducable. > > The tscdrift tool from jhb (in tools/tools/tscdrift) looks thus: > > root@appollyon:~/src/tscdrift # ./tscdrift > > CPU | TSC skew (min/avg/max/stddev) > > ----+------------------------------ > > 0 | 0 0 0 0.000 > 1 | 34 79 380 39.005 > 2 | 306 476 1326 120.472 > 3 | 306 485 1426 123.487 > 4 | 280 473 7500 248.965 > 5 | 280 462 1320 126.691 > 6 | 300 461 1934 129.362 > 7 | 300 470 1354 122.654 > 8 | 292 420 3640 152.029 > 9 | 135 190 655 58.601 > 10 | 112 188 620 56.490 > 11 | 114 189 660 62.440 > 12 | 129 204 566 53.731 > 13 | 129 206 617 56.047 > 14 | 126 211 620 54.450 > 15 | 126 213 603 54.808 > 16 | 440 590 1683 217.649 > 17 | 440 612 1606 234.295 > 18 | 468 642 4017 266.768 > 19 | 463 653 8683 352.624 > 20 | 480 671 1500 255.395 > 21 | 480 689 8060 348.384 > 22 | 468 707 3766 296.721 > 23 | 466 703 1683 284.625 > 24 | 480 767 8183 373.741 > 25 | 486 782 7400 362.069 > 26 | 480 664 1620 249.125 > 27 | 477 686 3669 278.144 > 28 | 469 621 1897 226.673 > 29 | 469 649 8275 363.575 > 30 | 457 636 1835 250.005 > 31 | 451 641 4300 272.322 FYI, that looks fairly typical for a system whose TSC's are in sync in my experience. Is this a dual-package system? The fact that threads 9-15 are "closer" to 0 than 2-8 is a bit unusual, but the rest looks quite typical. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 24 00:38:18 2014 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4BC1E1B; Wed, 24 Sep 2014 00:38:18 +0000 (UTC) Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 86F429D; Wed, 24 Sep 2014 00:38:18 +0000 (UTC) Received: by mail-qa0-f50.google.com with SMTP id j7so2488719qaq.9 for ; Tue, 23 Sep 2014 17:38:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=blVURoQm9f0QjzACbZim0dXWIeM+gR5NxZGhReUJs9w=; b=i7XtAnGcZRalPMldDa4vkefRTF+TDUGmTu9OZCZLh9ocBEXQbckhC100uvAA7CvB+P 09ZBfXb03eTij5i2L0xL4yenjR5X6GvX1c8meoK0Q8KojNm1aPxCB0EF2PbacVvKdiIc 6l7dwclSstUk1eJX+2X7OScFKJxU6ubk7pFXHaSipA6MKo1zb7njcq37JYm9/8YS7hOL 7yrzUlA6wGL4aBcIQfcIkvJSem0mJ1vClbwYLd3BGp3yOslAjPnPW/c/KmmRITSh/plU skLmSeYtk9E01jAxSKL2zonkK6cFMmB6xN939tlbbIqpcHj7oLx7dWQlQ+Jz1KRer9mo JMNg== MIME-Version: 1.0 X-Received: by 10.140.85.112 with SMTP id m103mr5084573qgd.50.1411519097512; Tue, 23 Sep 2014 17:38:17 -0700 (PDT) Sender: hiren.panchasara@gmail.com Received: by 10.96.168.194 with HTTP; Tue, 23 Sep 2014 17:38:17 -0700 (PDT) In-Reply-To: <5408938E.5020005@yandex.ru> References: <5408938E.5020005@yandex.ru> Date: Tue, 23 Sep 2014 17:38:17 -0700 X-Google-Sender-Auth: e8vZbY5iB2nB0u3jMzBJG5VlIUU Message-ID: Subject: Re: IOAT driver for FreeBSD From: hiren panchasara To: "Andrey V. Elsukov" , Jim Harris Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , Vijay Singh X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2014 00:38:18 -0000 + Jim On Thu, Sep 4, 2014 at 9:30 AM, Andrey V. Elsukov wrote: > On 03.09.2014 20:59, Vijay Singh wrote: >> Hi All, I found some discussion in the past about this. Is there a version >> of such a driver that I can test, and hopefully help get committed? > > There was some work in > http://svnweb.freebsd.org/base/user/jimharris/ioat/sys/dev/ioat/ Hi Jim, Whats the status of this user branch? cheers, Hiren From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 25 01:19:07 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D8CD95AF; Thu, 25 Sep 2014 01:19:07 +0000 (UTC) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F00FA83B; Thu, 25 Sep 2014 01:19:06 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id fb4so7966043wid.15 for ; Wed, 24 Sep 2014 18:19:05 -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:content-type; bh=8tZOTS76UArNEQSLjc/yoE3VEll0sT926E0wtD+XCH8=; b=PYdTWTos2MqL5Ttk8RVBUriosECo38q5sv0wlfUPWNqg7ojVQ+aAzrQnNq/QyVP9Rl 3NShV+/KNNVgPgg9EqF9LQbpBTJGz05YqdVnmhVibaaEKbPjASe5QvtRozrux2+bXMUn KL9aCzCyfv5o5WwFW+Ih+UGfQr83YH1VjNmys6ac1gfPbFh5TXGovGn8m/zwtN9v2uJH yOR2pUZgk7bhN0zgEK0y8tC26hr2JaU2wnj7xz2N7z2wprHq2EnuP3AXJhuldDGQDilm TQcGTX5wkd+fj7QhM98g1Ksqa+ZBzFB/Kn7j4lG64WAgLR6iGMCk9NatL0QbWCBDNfS2 sPKg== MIME-Version: 1.0 X-Received: by 10.194.219.193 with SMTP id pq1mr11996818wjc.5.1411607945105; Wed, 24 Sep 2014 18:19:05 -0700 (PDT) Received: by 10.194.161.228 with HTTP; Wed, 24 Sep 2014 18:19:05 -0700 (PDT) In-Reply-To: <53FBC329.6020107@freebsd.org> References: <3D62F4F4-ECCF-4622-BB57-D028160F3451@freebsd.org> <157901cfbe83$6cbf18d0$463d4a70$@FreeBSD.org> <16e101cfbfee$42b3b930$c81b2b90$@FreeBSD.org> <5FE57E4E-A627-4ABA-AB73-F0D60A3602D5@ixsystems.com> <236878C4-2C3E-4744-A04B-736C91032BFC@felyko.com> <96E32478-5450-4A35-B68A-4791668AA701@ixsystems.com> <53FBC329.6020107@freebsd.org> Date: Wed, 24 Sep 2014 22:19:05 -0300 Message-ID: Subject: Re: Lua in the bootloader From: Pedro Arthur To: Pedro Giffuni X-Mailman-Approved-At: Thu, 25 Sep 2014 01:37:14 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "Wojciech A. Koszek" , "" , "" , Jordan Hubbard , Rui Paulo X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2014 01:19:08 -0000 Hi, I've done some updates about the issues (1,2, 4, 6, 8) reviewed. I would like you to review these changes, following is my wiki page updated and the files changed. wiki head/sys/boot/lua/core.lua head/sys/boot/lua/menu.lua head/sys/boot/lua/screen.lua Thanks, Pedro. 2014-08-25 20:13 GMT-03:00 Pedro Giffuni : > > On 08/25/14 01:27, Jordan Hubbard wrote: > >> ... >> >>> The limitation of the dictionary and the size of the stack isn't the >>> main reason why I would prefer lua over forth. Why do we need to subje= ct >>> ourselves to a stack based language in 2014? The very limited number o= f >>> people hacking on the Forth boot loader on FreeBSD might have a differe= nt >>> opinion, but the language is so arcane that I fail to see why we should= n't >>> replace it. >>> >> Again, no disagreement, though I do wonder how many Lua programmers >> FreeBSD has that will be able to hit the ground running as a result of t= his >> evolution. Anyone? Raise your hands! I can=E2=80=99t raise mine - I= =E2=80=99ve never >> used Lua. :) >> >> - Jordan >> > > One one hand we have Forth which seems to be under-appreciated. I would > think that it is still better than nothing, but then nothing is what othe= r > people use and they are not complaining (perhaps because they don't know > what they are missing? I don't know). > > On the other hand there is Lua: If we do a quick look in the net for Lua > related code we can find many examples. It seems like there is a new > generation of game developers that are very fond of Lua, to the point tha= t > it is more popular than Python in gaming. Other than Angry Birds, I am al= so > seeing Lua embedded in Apache httpd, Trafficserver, VLC, there is even a > Forth implemented in Lua! To put it someway: Lua absolutely looks better > than forth in your resume. > > FWIW, although somewhat oldish, this looks like an interesting thing to > play with > http://lua-cui.sourceforge.net/ > > And there's also this: > https://code.google.com/p/llvm-lua/ > > No equivalents for Forth, AFAICT. > > This said, while Lua seems to be powerful and exciting, it is not the > mighty thing we want everywhere. Apparently Grub2 at some point embedded > Lua and later reverted it. NetBSD introduced Lua in their kernel but > apparently has found no use for it. DragonFly's installer had an old Lua > backend that they removed (they also removed bootforth very early). > > Options are good, I welcome the Lua option and I will love to see how far > it goes but let's not get too excited about the imminent death of Forth > just yet. Ultimately, being Devin the driving force behind the bootloader > enhancements, I think he is in the best position to choose. > > Pedro. > From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 25 03:32:02 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 50051A46; Thu, 25 Sep 2014 03:32:02 +0000 (UTC) Received: from outbound-smtp.edu.lahti.fi (outbound-smtp.edu.lahti.fi [143.51.142.38]) by mx1.freebsd.org (Postfix) with ESMTP id 0924E7ED; Thu, 25 Sep 2014 03:32:01 +0000 (UTC) Received: from edu.lahti.fi (unknown [109.95.47.233]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by inbound-smtp.edu.lahti.fi (Postfix) with ESMTPSA id A0FB8480DC0; Thu, 25 Sep 2014 06:31:49 +0300 (EEST) Message-ID: <3769C3A941E7152E07B05F1542B29085@edu.lahti.fi> From: "Joe Nosay" To: "Adrian Chadd" , "ISO 8859 1 Q Ermal Lu E7i" , "chromium" , "ppc" , "FreeBSD Hackers" , "CeDeROM" , "USAR VET" , "gecko" Subject: =?ISO-8859-1?Q?FW=3A=09Adrian_Chadd?= Date: Wed, 25 Sep 2014 04:31:49 +0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3522.110 X-MIMEOLE: Produced By Microsoft MimeOLE V16.4.3522.110 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2014 03:32:02 -0000 http://antiq.co.il/koyzzu/afqiqruhwbgmoaewqtdyitufwiupqnntlbhvhnh From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 25 23:41:48 2014 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2720A7C9; Thu, 25 Sep 2014 23:41:48 +0000 (UTC) Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C88BC229; Thu, 25 Sep 2014 23:41:47 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id uz6so6697931obc.3 for ; Thu, 25 Sep 2014 16:41:46 -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:content-type; bh=qPNK9+dihs5bJOyac3kIozon/Nv72rNt4G6htL/tcqU=; b=AxUIe6vLmFLsu7HPAm+yLrhiqb9cGuSiMN4pv3+By487ETt/0y/QzmyhfsFsgkGcdK 2w56GWpO6FLI47SoROSSNjyH9xSp05/GkBCaNJyCulQqvS0SSqh6c1Hq/eSeZ7IqJh+H APIcG76/CiUOdV9lBuzJRtv1H7+ReTxgfgqCIQtlIOd5i9fLFowpYCPLVMD0SEN8q5d9 kGqdA6+iq/1UJXaeGHi8ebbCbj4zZbkTvuX6EscjR5XfOGqy1fz8GX6ClesErLXZCaWp s10ZRF/ahhyd4nXqci3r7Mhstp1BiNaStkJQOq/ypmXREDFdjeU6FrPvU8HxX2KtIj31 ihUw== MIME-Version: 1.0 X-Received: by 10.182.20.177 with SMTP id o17mr14151912obe.59.1411688506908; Thu, 25 Sep 2014 16:41:46 -0700 (PDT) Received: by 10.202.188.84 with HTTP; Thu, 25 Sep 2014 16:41:46 -0700 (PDT) In-Reply-To: References: <5408938E.5020005@yandex.ru> Date: Thu, 25 Sep 2014 16:41:46 -0700 Message-ID: Subject: Re: IOAT driver for FreeBSD From: Jim Harris To: hiren panchasara Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-hackers@freebsd.org" , "Andrey V. Elsukov" , Vijay Singh X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2014 23:41:48 -0000 On Tue, Sep 23, 2014 at 5:38 PM, hiren panchasara wrote: > + Jim > > On Thu, Sep 4, 2014 at 9:30 AM, Andrey V. Elsukov > wrote: > > On 03.09.2014 20:59, Vijay Singh wrote: > >> Hi All, I found some discussion in the past about this. Is there a > version > >> of such a driver that I can test, and hopefully help get committed? > > > > There was some work in > > http://svnweb.freebsd.org/base/user/jimharris/ioat/sys/dev/ioat/ > > Hi Jim, > > Whats the status of this user branch? > > cheers, > Hiren > This user branch is a couple of years old, but should not be too difficult to bring forward to HEAD. It only includes E5 v1 (Sandy Bridge Xeon) device IDs so would need to be updated to include E5 v2 (Ivy Bridge) and v3 (Haswell) device IDs. Note this driver only does DMA operations currently and is not plumbed for other opcodes (XOR/P+Q, CRC, etc.) But the general framework is there to add code for the other opcodes. E5 v2 and v3 device IDs are pasted below. -Jim #define PCI_DEVICE_ID_INTEL_IOAT_IVB0 0x0e20 #define PCI_DEVICE_ID_INTEL_IOAT_IVB1 0x0e21 #define PCI_DEVICE_ID_INTEL_IOAT_IVB2 0x0e22 #define PCI_DEVICE_ID_INTEL_IOAT_IVB3 0x0e23 #define PCI_DEVICE_ID_INTEL_IOAT_IVB4 0x0e24 #define PCI_DEVICE_ID_INTEL_IOAT_IVB5 0x0e25 #define PCI_DEVICE_ID_INTEL_IOAT_IVB6 0x0e26 #define PCI_DEVICE_ID_INTEL_IOAT_IVB7 0x0e27 #define PCI_DEVICE_ID_INTEL_IOAT_IVB8 0x0e2e #define PCI_DEVICE_ID_INTEL_IOAT_IVB9 0x0e2f #define PCI_DEVICE_ID_INTEL_IOAT_HSW0 0x2f20 #define PCI_DEVICE_ID_INTEL_IOAT_HSW1 0x2f21 #define PCI_DEVICE_ID_INTEL_IOAT_HSW2 0x2f22 #define PCI_DEVICE_ID_INTEL_IOAT_HSW3 0x2f23 #define PCI_DEVICE_ID_INTEL_IOAT_HSW4 0x2f24 #define PCI_DEVICE_ID_INTEL_IOAT_HSW5 0x2f25 #define PCI_DEVICE_ID_INTEL_IOAT_HSW6 0x2f26 #define PCI_DEVICE_ID_INTEL_IOAT_HSW7 0x2f27 #define PCI_DEVICE_ID_INTEL_IOAT_HSW8 0x2f2e #define PCI_DEVICE_ID_INTEL_IOAT_HSW9 0x2f2f From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 26 06:40:22 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 267958DA for ; Fri, 26 Sep 2014 06:40:22 +0000 (UTC) Received: from mail.beastielabs.net (unknown [IPv6:2001:888:1227:0:200:24ff:fec9:5934]) (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 CA8FB26B for ; Fri, 26 Sep 2014 06:40:21 +0000 (UTC) Received: from beastie.hotsoft.nl (beastie.hotsoft.nl [IPv6:2001:888:1227:0:219:d1ff:fee8:91eb]) by mail.beastielabs.net (8.14.7/8.14.7) with ESMTP id s8Q6eGqZ066275 for ; Fri, 26 Sep 2014 08:40:17 +0200 (CEST) (envelope-from hans@beastielabs.net) Message-ID: <54250A50.1000607@beastielabs.net> Date: Fri, 26 Sep 2014 08:40:16 +0200 From: Hans Ottevanger User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Fwd: Autofs: spurious (?) log messages and zombies from automountd References: <54226E4D.1040704@beastielabs.net> In-Reply-To: <54226E4D.1040704@beastielabs.net> X-Forwarded-Message-Id: <54226E4D.1040704@beastielabs.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2014 06:40:22 -0000 Reposting here (with typos in subject corrected) after no response from stable@ for almost two days. Regards, Hans -------- Forwarded Message -------- Subject: Aitofs: spurious (?) jog messages and zombies from automountd Date: Wed, 24 Sep 2014 09:10:05 +0200 From: Hans Ottevanger To: freebsd-stable@FreeBSD.org Hi, When accessing a directory for the first time on /net, automounted using the new autofs, I reproducibly get error messages in the log. I have exported a single directory (read/write) from my test server: $ showmount -e soekris Exports list on soekris: /home My client runs 10-STABLE, also known as 10.1-BETA2 these days, updated to r272021. The kernel config is GENERIC minus devices that I do not have, with AUTOFS added. When accessing the server for the first time using: ls /net/soekris/home/hans I get the expected directory listing but immediately also see the following in /var/log/messages: Sep 24 07:39:09 beastie automountd[1554]: child process 2096 terminated with exit status 1 Sep 24 07:39:09 beastie automountd[1554]: child process 2101 terminated with exit status 1 Additionally, a zombie process keep hanging forever: $ pstree 1554 -+= 01554 root /usr/sbin/automountd \--- 02106 root When I wait until the directory is autounmounted and retry the access, the zombie disappears (apparently finally waited for) and I get two others in return: $ pstree 1554 -+= 01554 root /usr/sbin/automountd |--- 02658 root \--- 02663 root and a few extra log messages: Sep 24 08:52:17 beastie automountd[1554]: child process 2106 terminated with exit status 1 Sep 24 08:52:17 beastie automountd[1554]: child process 2653 terminated with exit status 1 Is anyone else seeing this? Do I miss something? Is this expected behavior? Kind regards, Hans _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 26 09:00:59 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0F247ACF for ; Fri, 26 Sep 2014 09:00:59 +0000 (UTC) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 87C9D7A9 for ; Fri, 26 Sep 2014 09:00:58 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id ty20so1582852lab.27 for ; Fri, 26 Sep 2014 02:00:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=zw6TCFlCO9CUgJND2hc7pi+p8DdvkvrzyxZeVzhTbPw=; b=l0U2+SRg1mqWJr2Hmkstg/MfmBqTnsi0B0LJwyAeDzYn/MC/EfnPgRFGoTbCCDPD8g JrNTm1E0Hx/qGhEYzG1BCUWCsCm5/PznssxO9XirC/ttIQDX2KNx5Km3iRCHheHDtj39 Oi/zXbgy/Zfmv8Yj2r+5bN4I6daF6aKk57O11mOYY/Jk4Hk+/up4zwrjqFrFPvAjLJgs 2kL+vh9iBG09869IhEGumKVS5g6w1kj1DjQpuPX0zWsfGGfKhspFcAssv520TIKcIDlv 0u5mug5MBGG4Lzce3eNFSQz3FT3fdjTloQ2q2H3LQPvU/24RW4PqAhuZEeEdFc/Breqj Lhag== X-Received: by 10.152.21.6 with SMTP id r6mr18983562lae.6.1411722056556; Fri, 26 Sep 2014 02:00:56 -0700 (PDT) Received: from brick.home (adfm247.neoplus.adsl.tpnet.pl. [79.184.116.247]) by mx.google.com with ESMTPSA id as5sm1650659lac.46.2014.09.26.02.00.55 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 Sep 2014 02:00:56 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Fri, 26 Sep 2014 11:00:53 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: Hans Ottevanger Subject: Re: Fwd: Autofs: spurious (?) log messages and zombies from automountd Message-ID: <20140926090053.GA10644@brick.home> Mail-Followup-To: Hans Ottevanger , freebsd-hackers@freebsd.org References: <54226E4D.1040704@beastielabs.net> <54250A50.1000607@beastielabs.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54250A50.1000607@beastielabs.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2014 09:00:59 -0000 On 0926T0840, Hans Ottevanger wrote: > Reposting here (with typos in subject corrected) after no response from > stable@ for almost two days. > > Regards, > > Hans > > > -------- Forwarded Message -------- > Subject: Aitofs: spurious (?) jog messages and zombies from automountd > Date: Wed, 24 Sep 2014 09:10:05 +0200 > From: Hans Ottevanger > To: freebsd-stable@FreeBSD.org > > Hi, > > When accessing a directory for the first time on /net, automounted using > the new autofs, I reproducibly get error messages in the log. > > I have exported a single directory (read/write) from my test server: > > $ showmount -e soekris > > Exports list on soekris: > /home > > My client runs 10-STABLE, also known as 10.1-BETA2 these days, updated > to r272021. The kernel config is GENERIC minus devices that I do not > have, with AUTOFS added. > > When accessing the server for the first time using: > > ls /net/soekris/home/hans > > I get the expected directory listing but immediately also see the > following in /var/log/messages: > > Sep 24 07:39:09 beastie automountd[1554]: child process 2096 terminated > with exit status 1 > Sep 24 07:39:09 beastie automountd[1554]: child process 2101 terminated > with exit status 1 There are no log messages preceding this? > Additionally, a zombie process keep hanging forever: > > $ pstree 1554 > -+= 01554 root /usr/sbin/automountd > \--- 02106 root > > When I wait until the directory is autounmounted and retry the access, > the zombie disappears (apparently finally waited for) and I get two > others in return: > > $ pstree 1554 > -+= 01554 root /usr/sbin/automountd > |--- 02658 root > \--- 02663 root > > and a few extra log messages: > > Sep 24 08:52:17 beastie automountd[1554]: child process 2106 terminated > with exit status 1 > Sep 24 08:52:17 beastie automountd[1554]: child process 2653 terminated > with exit status 1 > > Is anyone else seeing this? > Do I miss something? > Is this expected behavior? Not quite; I'll try to reproduce it. From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 26 10:32:31 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1D65AA42; Fri, 26 Sep 2014 10:32:31 +0000 (UTC) Received: from mail.beastielabs.net (unknown [IPv6:2001:888:1227:0:200:24ff:fec9:5934]) (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 BCE4B281; Fri, 26 Sep 2014 10:32:30 +0000 (UTC) Received: from beastie.hotsoft.nl (beastie.hotsoft.nl [IPv6:2001:888:1227:0:219:d1ff:fee8:91eb]) by mail.beastielabs.net (8.14.7/8.14.7) with ESMTP id s8QAWR5G067122; Fri, 26 Sep 2014 12:32:27 +0200 (CEST) (envelope-from hans@beastielabs.net) Message-ID: <542540BB.80001@beastielabs.net> Date: Fri, 26 Sep 2014 12:32:27 +0200 From: Hans Ottevanger User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: =?UTF-8?B?RWR3YXJkIFRvbWFzeiBOYXBpZXJhxYJh?= Subject: Re: Fwd: Autofs: spurious (?) log messages and zombies from automountd References: <54226E4D.1040704@beastielabs.net> <54250A50.1000607@beastielabs.net> <20140926090053.GA10644@brick.home> In-Reply-To: <20140926090053.GA10644@brick.home> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2014 10:32:31 -0000 On 09/26/14 11:00, Edward Tomasz Napierała wrote: > On 0926T0840, Hans Ottevanger wrote: >> Reposting here (with typos in subject corrected) after no response from >> stable@ for almost two days. >> >> Regards, >> >> Hans >> >> >> -------- Forwarded Message -------- >> Subject: Aitofs: spurious (?) jog messages and zombies from automountd >> Date: Wed, 24 Sep 2014 09:10:05 +0200 >> From: Hans Ottevanger >> To: freebsd-stable@FreeBSD.org >> >> Hi, >> >> When accessing a directory for the first time on /net, automounted using >> the new autofs, I reproducibly get error messages in the log. >> >> I have exported a single directory (read/write) from my test server: >> >> $ showmount -e soekris >> >> Exports list on soekris: >> /home >> >> My client runs 10-STABLE, also known as 10.1-BETA2 these days, updated >> to r272021. The kernel config is GENERIC minus devices that I do not >> have, with AUTOFS added. >> >> When accessing the server for the first time using: >> >> ls /net/soekris/home/hans >> >> I get the expected directory listing but immediately also see the >> following in /var/log/messages: >> >> Sep 24 07:39:09 beastie automountd[1554]: child process 2096 terminated >> with exit status 1 >> Sep 24 07:39:09 beastie automountd[1554]: child process 2101 terminated >> with exit status 1 > > There are no log messages preceding this? > No. Just the normal messages logged at boot time. >> Additionally, a zombie process keep hanging forever: >> >> $ pstree 1554 >> -+= 01554 root /usr/sbin/automountd >> \--- 02106 root >> >> When I wait until the directory is autounmounted and retry the access, >> the zombie disappears (apparently finally waited for) and I get two >> others in return: >> >> $ pstree 1554 >> -+= 01554 root /usr/sbin/automountd >> |--- 02658 root >> \--- 02663 root >> >> and a few extra log messages: >> >> Sep 24 08:52:17 beastie automountd[1554]: child process 2106 terminated >> with exit status 1 >> Sep 24 08:52:17 beastie automountd[1554]: child process 2653 terminated >> with exit status 1 >> >> Is anyone else seeing this? >> Do I miss something? >> Is this expected behavior? > > Not quite; I'll try to reproduce it. > I planned to make a new CURRENT snapshot installation on another machine anyhow today. I will see what happens there. Kind regards, Hans From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 26 11:39:26 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CFD382A1; Fri, 26 Sep 2014 11:39:26 +0000 (UTC) Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8BC76C65; Fri, 26 Sep 2014 11:39:26 +0000 (UTC) Received: by mail-ob0-f170.google.com with SMTP id wp4so512570obc.15 for ; Fri, 26 Sep 2014 04:39:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=6BRQLlR6PCYFfyhGYUKvtdIHFHgOBK31vwQ3Mq/ik1A=; b=yPTQlBtuJ+kNzOPMnwGXreNDsMqHjAIP3KaiTal8V1xB59ZoKHV4tW6v6ZwmiNhTZT zcg405NM8aJfMJJtXuZ5bR6YVIOzLOWCFycwuIFus71R40XZtid/UND2agAgwkovzh10 y/8Mz5X/MJqbNzpMSXpYKJHhHkn0cFReyX/vHluohuoihWfodNwwmNGJ+Qkt7ToCFqal xeoxCzcU1CSnac3AplpYE09ikUsHDiijGpcRDGS82ZwTIu5c0iSNZ0LCsiWA8dIj77nS Z+3LTCQAIchf5/D4VZYlOXnlXmj2CqDmkQCfwzYZChatOmoGZ65YJIwBDY8sve2liDY1 ypuw== MIME-Version: 1.0 X-Received: by 10.60.176.169 with SMTP id cj9mr13045282oec.21.1411731565917; Fri, 26 Sep 2014 04:39:25 -0700 (PDT) Sender: tomek.cedro@gmail.com Received: by 10.202.58.196 with HTTP; Fri, 26 Sep 2014 04:39:25 -0700 (PDT) In-Reply-To: References: Date: Fri, 26 Sep 2014 13:39:25 +0200 X-Google-Sender-Auth: bqtN4-5V-UzX1Bny6x8Smv5OAiA Message-ID: Subject: Re: FreeBSD and WiDi / Miracast / WiFi Direct HDMI streaming From: CeDeROM To: Waitman Gobble Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , FreeBSD Questions Mailing List X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2014 11:39:26 -0000 On Wed, Sep 17, 2014 at 11:06 AM, CeDeROM wrote: > I have just received a Chromecast from Google dongle =) IT WORKS! > Amazingly from start, on my old Nexus7, seems to work on OSX as well. > Now time for FreeBSD :-) Good news - Chromecast does work like a charm. Good news - Chromium has this nice "CAST" extension that allows to render website and stream it via Chromecast. Its then recognised by Youtube player itself. It works nice with OSX. Bad news - Cast extension crashes Chromium (Version 37.0.2062.94 (290621) (64-bit)) just after install on FreeBSD (10.0-RELEASE AMD64). Still, something is already out there, just need some tuning, it seems :-) Maybe a new release of Chromium will bring fixes and no work is even necessary :-) Best regards! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 26 14:51:39 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2DD87BF4 for ; Fri, 26 Sep 2014 14:51:39 +0000 (UTC) Received: from ustc.edu.cn (email6.ustc.edu.cn [IPv6:2001:da8:d800::8]) by mx1.freebsd.org (Postfix) with ESMTP id 30889788 for ; Fri, 26 Sep 2014 14:51:37 +0000 (UTC) Received: by ajax-webmail-newmailweb.ustc.edu.cn (Coremail) ; Fri, 26 Sep 2014 22:51:36 +0800 (GMT+08:00) X-CM-HeaderCharset: UTF-8 X-Originating-IP: [58.211.218.74] Date: Fri, 26 Sep 2014 22:51:36 +0800 (GMT+08:00) From: btw@mail.ustc.edu.cn To: freebsd-hackers Subject: Questions with the in_cksumdata() function in sys/amd64/amd64/in_cksum.c X-Priority: 3 X-Mailer: Coremail Webmail Server Version XT3.0.4a build 20140813(28498.6655.6441) Copyright (c) 2002-2014 www.mailtech.cn ustc-xl X-SendMailWithSms: false Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8 MIME-Version: 1.0 Message-ID: <3225c531.3abe.148b2721f15.Coremail.btw@mail.ustc.edu.cn> X-CM-TRANSID: LkAmygCXeYp4fSVUzYgGAA--.1169W X-CM-SenderInfo: xewzqzxdloh3xvwfhvlgxou0/1tbiAQUTAVQhl71ibgACsH X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2014 14:51:39 -0000 Hi All, I'm reading the in_cksumdata() function in sys/amd64/amd64/in_cksum.c, and I have some questions with the following comment and code: static u_int64_t in_cksumdata(const void *buf, int len) { ...... /* * access prefilling to start load of next cache line. * then add current cache line * save result of prefilling for loop iteration. */ prefilled = lw[0]; while ((len -= 32) >= 4) { u_int64_t prefilling = lw[8]; sum += prefilled + lw[1] + lw[2] + lw[3] + lw[4] + lw[5] + lw[6] + lw[7]; lw += 8; prefilled = prefilling; } ...... } It said that it adds the current cache line, and it adds 32 bytes actually, while on amd64 platform, the size of each cache line is 64 bytes. So I think the correct code should be something like this: static u_int64_t in_cksumdata(const void *buf, int len) { ...... /* * access prefilling to start load of next cache line. * then add current cache line * save result of prefilling for loop iteration. */ prefilled = lw[0]; while ((len -= 64) >= 4) { u_int64_t prefilling = lw[16]; sum += prefilled + lw[1] + lw[2] + lw[3] + lw[4] + lw[5] + lw[6] + lw[7] + lw[8] + lw[9] + lw[10] + lw[11] + lw[12] + lw[13] + lw[14] + lw[15]; lw += 16; prefilled = prefilling; } ...... } The full patch is: diff --git a/in_cksum.c b/in_cksum.c index 2ae3a0c..4f141f8 100644 --- a/in_cksum.c +++ b/in_cksum.c @@ -140,19 +140,23 @@ in_cksumdata(const void *buf, int len) * save result of prefilling for loop iteration. */ prefilled = lw[0]; - while ((len -= 32) >= 4) { - u_int64_t prefilling = lw[8]; + while ((len -= 64) >= 4) { + u_int64_t prefilling = lw[16]; sum += prefilled + lw[1] + lw[2] + lw[3] - + lw[4] + lw[5] + lw[6] + lw[7]; - lw += 8; + + lw[4] + lw[5] + lw[6] + lw[7] + + lw[8] + lw[9] + lw[10] + lw[11] + + lw[12] + lw[13] + lw[14] + lw[15]; + lw += 16; prefilled = prefilling; } if (len >= 0) { sum += prefilled + lw[1] + lw[2] + lw[3] - + lw[4] + lw[5] + lw[6] + lw[7]; - lw += 8; + + lw[4] + lw[5] + lw[6] + lw[7] + + lw[8] + lw[9] + lw[10] + lw[11] + + lw[12] + lw[13] + lw[14] + lw[15]; + lw += 16; } else { - len += 32; + len += 64; } while ((len -= 16) >= 0) { sum += (u_int64_t) lw[0] + lw[1] + lw[2] + lw[3]; Sorry about the confusion if I did something wrong. - twb From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 26 15:06:34 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72985106; Fri, 26 Sep 2014 15:06:34 +0000 (UTC) Received: from mail.beastielabs.net (unknown [IPv6:2001:888:1227:0:200:24ff:fec9:5934]) (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 91BB090E; Fri, 26 Sep 2014 15:06:33 +0000 (UTC) Received: from beastie.hotsoft.nl (beastie.hotsoft.nl [IPv6:2001:888:1227:0:219:d1ff:fee8:91eb]) by mail.beastielabs.net (8.14.7/8.14.7) with ESMTP id s8QF6Umc067783; Fri, 26 Sep 2014 17:06:30 +0200 (CEST) (envelope-from hans@beastielabs.net) Message-ID: <542580F6.7030609@beastielabs.net> Date: Fri, 26 Sep 2014 17:06:30 +0200 From: Hans Ottevanger User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: =?UTF-8?B?RWR3YXJkIFRvbWFzeiBOYXBpZXJhxYJh?= Subject: Re: Fwd: Autofs: spurious (?) log messages and zombies from automountd References: <54226E4D.1040704@beastielabs.net> <54250A50.1000607@beastielabs.net> <20140926090053.GA10644@brick.home> <542540BB.80001@beastielabs.net> In-Reply-To: <542540BB.80001@beastielabs.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2014 15:06:34 -0000 On 09/26/14 12:32, Hans Ottevanger wrote: > On 09/26/14 11:00, Edward Tomasz Napierała wrote: >> On 0926T0840, Hans Ottevanger wrote: [...] > > I planned to make a new CURRENT snapshot installation on another machine > anyhow today. I will see what happens there. > I just verified that with fresh installations of both 10.1-BETA2 and the latest CURRENT snapshot (based on r271779) the same issue occurs. Kind regards, Hans From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 26 17:10:42 2014 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB307C3; Fri, 26 Sep 2014 17:10:42 +0000 (UTC) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 670E3926; Fri, 26 Sep 2014 17:10:42 +0000 (UTC) Received: by mail-oi0-f42.google.com with SMTP id u20so10049227oif.29 for ; Fri, 26 Sep 2014 10:10:41 -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:content-type; bh=RtJwlHdBw8KvAzYxITp4dm+0yBabEnruZjzR35yIiW8=; b=xAq4LcMKiSpbHOflGYK0JAq7jFA5h1BEwOK348wX1Zr0yeT7Znq0WtEsrI2MOwkIv7 jAhWnSFnMrrpkAjN1tSXaUEwyjqvbr803Z7GwJI1wSsp5ArGfodsCIF+/CcfbGjKw9D4 EiVb9fng/W3f/q33Q+UUXcihLA6+mcGCvF1UvsO6AuoFVJlS2DHpgTucFCXRGzL+iY6H ZgtiFuw+QaV+qJLeB4urlkBJf/0n4LxjM3JMUdiJg9cfurW/Vi4+zZjGWpdL+QnfhMeg HGPGTEXScX+Zvw/XrTEwmML3x+aWGDTlhQg14nMYw/6rW+0pkyyQMUUvrUsZp4st8lqT wnJA== MIME-Version: 1.0 X-Received: by 10.182.105.167 with SMTP id gn7mr22377860obb.7.1411751441500; Fri, 26 Sep 2014 10:10:41 -0700 (PDT) Received: by 10.182.250.234 with HTTP; Fri, 26 Sep 2014 10:10:41 -0700 (PDT) In-Reply-To: References: <5408938E.5020005@yandex.ru> Date: Fri, 26 Sep 2014 10:10:41 -0700 Message-ID: Subject: Re: IOAT driver for FreeBSD From: Vijay Singh To: Jim Harris Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-hackers@freebsd.org" , "Andrey V. Elsukov" , hiren panchasara X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2014 17:10:42 -0000 Jim, since the device IDs were changed, were there any changes to the descriptors for the DMA part? =vijay On Thu, Sep 25, 2014 at 4:41 PM, Jim Harris wrote: > > > On Tue, Sep 23, 2014 at 5:38 PM, hiren panchasara > wrote: > >> + Jim >> >> On Thu, Sep 4, 2014 at 9:30 AM, Andrey V. Elsukov >> wrote: >> > On 03.09.2014 20:59, Vijay Singh wrote: >> >> Hi All, I found some discussion in the past about this. Is there a >> version >> >> of such a driver that I can test, and hopefully help get committed? >> > >> > There was some work in >> > >> http://svnweb.freebsd.org/base/user/jimharris/ioat/sys/dev/ioat/ >> >> Hi Jim, >> >> Whats the status of this user branch? >> >> cheers, >> Hiren >> > > This user branch is a couple of years old, but should not be too difficult > to bring forward to HEAD. It only includes E5 v1 (Sandy Bridge Xeon) > device IDs so would need to be updated to include E5 v2 (Ivy Bridge) and v3 > (Haswell) device IDs. > > Note this driver only does DMA operations currently and is not plumbed for > other opcodes (XOR/P+Q, CRC, etc.) But the general framework is there to > add code for the other opcodes. > > E5 v2 and v3 device IDs are pasted below. > > -Jim > > #define PCI_DEVICE_ID_INTEL_IOAT_IVB0 0x0e20 > > #define PCI_DEVICE_ID_INTEL_IOAT_IVB1 0x0e21 > > #define PCI_DEVICE_ID_INTEL_IOAT_IVB2 0x0e22 > > #define PCI_DEVICE_ID_INTEL_IOAT_IVB3 0x0e23 > > #define PCI_DEVICE_ID_INTEL_IOAT_IVB4 0x0e24 > > #define PCI_DEVICE_ID_INTEL_IOAT_IVB5 0x0e25 > > #define PCI_DEVICE_ID_INTEL_IOAT_IVB6 0x0e26 > > #define PCI_DEVICE_ID_INTEL_IOAT_IVB7 0x0e27 > > #define PCI_DEVICE_ID_INTEL_IOAT_IVB8 0x0e2e > > #define PCI_DEVICE_ID_INTEL_IOAT_IVB9 0x0e2f > > #define PCI_DEVICE_ID_INTEL_IOAT_HSW0 0x2f20 > > #define PCI_DEVICE_ID_INTEL_IOAT_HSW1 0x2f21 > > #define PCI_DEVICE_ID_INTEL_IOAT_HSW2 0x2f22 > > #define PCI_DEVICE_ID_INTEL_IOAT_HSW3 0x2f23 > > #define PCI_DEVICE_ID_INTEL_IOAT_HSW4 0x2f24 > > #define PCI_DEVICE_ID_INTEL_IOAT_HSW5 0x2f25 > > #define PCI_DEVICE_ID_INTEL_IOAT_HSW6 0x2f26 > > #define PCI_DEVICE_ID_INTEL_IOAT_HSW7 0x2f27 > > #define PCI_DEVICE_ID_INTEL_IOAT_HSW8 0x2f2e > > #define PCI_DEVICE_ID_INTEL_IOAT_HSW9 0x2f2f > > From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 27 22:15:14 2014 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1DEB3D2; Sat, 27 Sep 2014 22:15:13 +0000 (UTC) Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6F14995; Sat, 27 Sep 2014 22:15:13 +0000 (UTC) Received: by mail-yh0-f45.google.com with SMTP id a41so4646339yho.32 for ; Sat, 27 Sep 2014 15:15:12 -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:content-type; bh=VB+ng4gitQhat1p5JQEZ840uyZir95NAp2rHLoiRud4=; b=VGKcz/Fa7n66OwtqZMHx59t06jDp7x+fB7VStN05Rvc1s+O7/GbDHtprsNyv5uAf+Z 4myWbenvRGEN6nqcOvpL3HIydC6T8PAdq/JcyDVtTQlYGHtQ9vv0E+BLTkto6/7ewlXe ci77gJfXE+p+mo16Av26/iDOy9ozPDi8Jt6i2hWvo9Fc8ju6i9ZznDtWdaxXKPo2oBWm vq1Kci3Wx86ITJJeH8FmWsTrB4uQBcleqE/Xh+ztBZQHERfHlHfVWk6FGdI2eRq5IYV/ ndIFxvaM+40EGvGww4KEZM/l60P4Ri7EDC2aT0t0ZnlWLsAyk5PxHSlAd4QEqU/Zz0A5 gDgw== MIME-Version: 1.0 X-Received: by 10.236.132.20 with SMTP id n20mr17611916yhi.94.1411856112705; Sat, 27 Sep 2014 15:15:12 -0700 (PDT) Received: by 10.170.206.10 with HTTP; Sat, 27 Sep 2014 15:15:12 -0700 (PDT) In-Reply-To: <1411851225.9364.YahooMailNeo@web180902.mail.ne1.yahoo.com> References: <1411851225.9364.YahooMailNeo@web180902.mail.ne1.yahoo.com> Date: Sat, 27 Sep 2014 15:15:12 -0700 Message-ID: Subject: Re: Inproper ada# assignment in 10-BETA2 From: Mehmet Erol Sanliturk To: Jin Guojun Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "hackers@freebsd.org" , questions freebsd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Sep 2014 22:15:14 -0000 On Sat, Sep 27, 2014 at 1:53 PM, Jin Guojun wrote: > Installed 10-BETA2 on SATA port 4 (ad8) and then added another SATA port 3 > (ad6), the system has not correctly enumerate the ada # for the boot device. > As original boot (without the second SATA drive), the ad8 is enumerated as > ada0 -- the boot drive: > > Sep 24 22:51:30 R10-B2 kernel: ada0 at ahcich2 bus 0 scbus2 target 0 lun 0 > Sep 24 22:51:30 R10-B2 kernel: ada0: > ATA-8 SATA 2.x device > ... > Sep 24 22:51:30 R10-B2 kernel: ada0: Previously was known as ad8 > > > However, after added another SATA drive (ad6), this new drive is assigned > to ada0, but ad8 has changed to ada1. This is incorrect dynamic device > assignment. FreeBSD has kept using fixed disk ID assignment due to the same > problem introduced in around 4-R (or may be slightly later), and after a > simple debate, a decision was made to use fixed drive ID to avoid such > hassle. > > If now we want to use dynamic enumeration for drive ID# assignment, this > has to be done correctly -- boot drive MUST assigned to 0 or whatever the # > as installation assigned to; otherwise, adding a new drive will cause > system not bootable, or make other existing drive not mountable due to > enumeration # changes. > > Has this been reported as a known problem for 10-R, or shall I open a bug > to track? > > -Jin > One point should be checked : On mainboards SATA ports are numbered from 0 or 1 to upward . BIOS always uses first SATA drive for boot . This is NOT related to the operating system . Therefore , it is necessary to check port numbers of existing drives and the bootable SATA drive should be connected to the smallest numbered SATA port among existent drives . For example , assume bootable drive is connected to SATA port 2 . New drive should be connected to a higher numbered SATA port . If there are only two SATA ports , then bootable drive should be connected to the first SATA port . If mainboard BIOS allows definition of any SATA port for boot , and bootable SATA port and drive is specified in there , again it may boot from that drive . Up to now , I did not see any BIOS which supplies such an ordering among SATA ports . Please check your BIOS for such a feature . If it is present you may use it , otherwise it is necessary to reconnect SATA cables . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 27 20:56:18 2014 Return-Path: Delivered-To: hackers@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 9A75F939 for ; Sat, 27 Sep 2014 20:56:18 +0000 (UTC) Received: from nm6-vm1.access.bullet.mail.gq1.yahoo.com (nm6-vm1.access.bullet.mail.gq1.yahoo.com [216.39.63.4]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6457AFC for ; Sat, 27 Sep 2014 20:56:17 +0000 (UTC) Received: from [216.39.60.165] by nm6.access.bullet.mail.gq1.yahoo.com with NNFMP; 27 Sep 2014 20:53:45 -0000 Received: from [216.39.60.243] by tm1.access.bullet.mail.gq1.yahoo.com with NNFMP; 27 Sep 2014 20:53:45 -0000 Received: from [127.0.0.1] by omp1014.access.mail.gq1.yahoo.com with NNFMP; 27 Sep 2014 20:53:45 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 770708.39495.bm@omp1014.access.mail.gq1.yahoo.com Received: (qmail 10853 invoked by uid 60001); 27 Sep 2014 20:53:45 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1411851225; bh=3LT5EZ0GALkM8fUp5bXb9S3yCdBBMcMTvc9GBeJlwEg=; h=Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=S5NtY3hwJolDX2nmyn5JUyB4BgLs2XGWAtQebS9/AcxUraaGfr0wz+X/ZMSFbiN6RwMGXhbzOWy8U6hN4okTlcKNmXEpjIzfi/K4Rch3y/bmJ+S4AW3egAHa9LzBrYGbmHlOpkMc3QNT9PNmwg0dOgVUCpjHPDdzcpo4zhHz77o= X-YMail-OSG: t2l2jLsVM1nVP2hS1BTHg54MycVu886E8SQzLynI_sOheyz SAkbxFBMGb0GcOa58gkT1kyig.IAYQVcTVYlyRjFhLTkWGiD8skEJexEwf_8 aR.nfTYUCqi9Rjlh0xeiANjJA3ffOf9HWcMG7vdloxYM0WRRhHvhhNqWu5B2 hGFyoVnPUjI17gHVW.ZB7F8ol.RS11SPvrHOcKQOd.Xz9RQT8fKyni2lPkZi GnhTkr4AK3J1yzlwDwLmM4.QuSuIAyXX28FpOiNPQJ8m2oJ6RAIqetNVsQkB lfUkVW60R1mY2kPSR1rWMDWpUm.IioZIULtrqUgiVMcyn_4u9c0xOpc0MtzU VeukVODVPPEJyFhPpaSFnW5p4ZbojEUooqENtC3LLA_qxTU7MnDzxG._Q8mY FcyYaM1F6N9CmzO9U5zt6hKQl3yhMAuFV.cmN9aYdn6FfkSMmK4WEok3_3FN omAx1pIO9UAFD26o0chCip0Y3GyaH0xZM6ZHxqvl5uYhFBfjJjkkKfBs4smw RpCZ9XxLVFgLzjFl8DW1Xb4vh9gEW.SXeUmMsL11sYV.6d1lGBC6YUGBDZh_ .RSOLgA7syQjD05Q- Received: from [162.239.0.170] by web180902.mail.ne1.yahoo.com via HTTP; Sat, 27 Sep 2014 13:53:45 PDT X-Rocket-MIMEInfo: 002.001, SW5zdGFsbGVkIDEwLUJFVEEyIG9uIFNBVEEgcG9ydCA0IChhZDgpIGFuZCB0aGVuIGFkZGVkIGFub3RoZXIgU0FUQSBwb3J0IDMgKGFkNiksIHRoZSBzeXN0ZW0gaGFzIG5vdCBjb3JyZWN0bHkgZW51bWVyYXRlIHRoZSBhZGEgIyBmb3IgdGhlIGJvb3QgZGV2aWNlLgpBcyBvcmlnaW5hbCBib290ICh3aXRob3V0IHRoZSBzZWNvbmQgU0FUQSBkcml2ZSksIHRoZSBhZDggaXMgZW51bWVyYXRlZCBhcyBhZGEwIC0tIHRoZSBib290IGRyaXZlOgoKU2VwIDI0IDIyOjUxOjMwIFIxMC1CMiBrZXJuZWw6IGFkYTAgYXQBMAEBAQE- X-Mailer: YahooMailWebService/0.8.203.696 Message-ID: <1411851225.9364.YahooMailNeo@web180902.mail.ne1.yahoo.com> Date: Sat, 27 Sep 2014 13:53:45 -0700 From: Jin Guojun Reply-To: Jin Guojun Subject: Inproper ada# assignment in 10-BETA2 To: questions freebsd , "hackers@freebsd.org" MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 27 Sep 2014 23:32:41 +0000 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Sep 2014 20:56:18 -0000 Installed 10-BETA2 on SATA port 4 (ad8) and then added another SATA port 3 (ad6), the system has not correctly enumerate the ada # for the boot device. As original boot (without the second SATA drive), the ad8 is enumerated as ada0 -- the boot drive: Sep 24 22:51:30 R10-B2 kernel: ada0 at ahcich2 bus 0 scbus2 target 0 lun 0 Sep 24 22:51:30 R10-B2 kernel: ada0: ATA-8 SATA 2.x device ... Sep 24 22:51:30 R10-B2 kernel: ada0: Previously was known as ad8 However, after added another SATA drive (ad6), this new drive is assigned to ada0, but ad8 has changed to ada1. This is incorrect dynamic device assignment. FreeBSD has kept using fixed disk ID assignment due to the same problem introduced in around 4-R (or may be slightly later), and after a simple debate, a decision was made to use fixed drive ID to avoid such hassle. If now we want to use dynamic enumeration for drive ID# assignment, this has to be done correctly -- boot drive MUST assigned to 0 or whatever the # as installation assigned to; otherwise, adding a new drive will cause system not bootable, or make other existing drive not mountable due to enumeration # changes. Has this been reported as a known problem for 10-R, or shall I open a bug to track? -Jin