Re: r324353: boot failure: failed with error 19

On Fri, 2017-10-06 at 22:33 +0200, O. Hartmann wrote: > First of all, I think something has changed, since /dev/ufs doesn't get > populated anymore > by usage of "gpart label" command. Second, there is a high chance that I > messed up > NanoBSD a bit, a couple of days ago I tried to sync with

Re: r324353: boot failure: failed with error 19

Am Fri, 6 Oct 2017 15:27:52 +0200 (CEST) Trond Endrestøl schrieb: > On Fri, 6 Oct 2017 15:10+0200, O. Hartmann wrote: > > > I run a small appliance on an APU from PCengines. This box is bootet via SD > > card, the > > image is created by a modified NanoBSD,

Re: r324353: boot failure: failed with error 19

Am Fri, 6 Oct 2017 07:10:44 -0700 Warner Losh schrieb: > On Fri, Oct 6, 2017 at 6:10 AM, O. Hartmann wrote: > > > I run a small appliance on an APU from PCengines. This box is bootet via > > SD card, the > > image is created by a modified NanoBSD, which

Re: RFC how to use kernel procs/threads efficiently

On Fri, 2017-10-06 at 19:02 +, Rick Macklem wrote: > Hi, > > I have now dropped the client side of Flexible File Layout for pNFS into head > and I believe it is basically working. > Currently when talking to mirrored DS servers, it does the Write and Commit > RPCs to the mirrors serially.

RFC how to use kernel procs/threads efficiently

Hi, I have now dropped the client side of Flexible File Layout for pNFS into head and I believe it is basically working. Currently when talking to mirrored DS servers, it does the Write and Commit RPCs to the mirrors serially. This works, but is inefficient w.r.t. elapsed to to completion. To

Re: C++ in jemalloc

On 2017-Oct-6, at 9:58 AM, Conrad Meyer wrote: > On Fri, Oct 6, 2017 at 9:17 AM, Ian Lepore wrote: >> It isn't about "a broken port". All C++ code is broken if exceptions >> don't work. That means devd is broken. Not to mention clang itself. >> It may be that neither of those relies on

Re: C++ in jemalloc

On Fri, Oct 6, 2017 at 9:17 AM, Ian Lepore wrote: > It isn't about "a broken port". All C++ code is broken if exceptions > don't work. That means devd is broken. Not to mention clang itself. > It may be that neither of those relies on exceptions for routine > operation and

Re: C++ in jemalloc

On Fri, 2017-10-06 at 09:04 -0700, Conrad Meyer wrote: > On Thu, Oct 5, 2017 at 9:58 PM, Mark Millard > wrote: > > > > Luckily most kernel and world code that I actively use > > does not throw C++ exceptions in my use. > > > > But devel/kyua is majorly broken by the C++

Re: C++ in jemalloc

On 2017-Oct-6, at 7:15 AM, Justin Hibbits wrote: > Hi Mark, > > On Thu, Oct 5, 2017 at 11:58 PM, Mark Millard wrote: >> Warner Losh imp at bsdimp.com wrote on >> Thu Oct 5 21:01:26 UTC 2017 : >> >>> Starting in FreeBSD 11, arm and powerpc are supported by clang, >>> but

Re: C++ in jemalloc

On Fri, Oct 6, 2017 at 9:17 AM, Ian Lepore wrote: > On Fri, 2017-10-06 at 09:04 -0700, Conrad Meyer wrote: > > On Thu, Oct 5, 2017 at 9:58 PM, Mark Millard > > wrote: > > > > > > Luckily most kernel and world code that I actively use > > > does not throw

Re: C++ in jemalloc

On Thu, Oct 5, 2017 at 9:58 PM, Mark Millard wrote: > Luckily most kernel and world code that I actively use > does not throw C++ exceptions in my use. > > But devel/kyua is majorly broken by the C++ exception > issue: It makes extensive use of C++ exceptions. In my > view

Re: C++ in jemalloc

Hi Mark, On Thu, Oct 5, 2017 at 11:58 PM, Mark Millard wrote: > Warner Losh imp at bsdimp.com wrote on > Thu Oct 5 21:01:26 UTC 2017 : > >> Starting in FreeBSD 11, arm and powerpc are supported by clang, >> but not super well. For FreeBSD 12, we're getting close for

Re: r324353: boot failure: failed with error 19

On Fri, Oct 6, 2017 at 6:10 AM, O. Hartmann wrote: > I run a small appliance on an APU from PCengines. This box is bootet via > SD card, the > image is created by a modified NanoBSD, which creates GPT/UEFI > partitioning and booting > images. > > That worked until two

Re: r324353: boot failure: failed with error 19

On Fri, 6 Oct 2017 15:10+0200, O. Hartmann wrote: > I run a small appliance on an APU from PCengines. This box is bootet via SD > card, the > image is created by a modified NanoBSD, which creates GPT/UEFI partitioning > and booting > images. > > That worked until two days ago (I do not track

r324353: boot failure: failed with error 19

I run a small appliance on an APU from PCengines. This box is bootet via SD card, the image is created by a modified NanoBSD, which creates GPT/UEFI partitioning and booting images. That worked until two days ago (I do not track the revision numer) when I wrote (via dd) the last image out.

Re: C++ in jemalloc

On Thu, Oct 05, 2017 at 11:59:03AM -0700, David Goldblatt wrote: > Hi all, > > The jemalloc developers have wanted to start using C++ for a while, to > enable some targeted refactorings of code we have trouble maintaining due > to brittleness or complexity (e.g. moving thousand line macro