Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On Wednesday 05 April 2017 16:15:41 Alexey Dokuchaev wrote: > On Thu, Mar 30, 2017 at 07:26:43PM +0200, Matthew Rezny wrote: > > LLVM 3.8 introduced the option to build a shared LLVM library, which is > > what Mesa needs for use at runtime (for e.g. compiling shaders), separate &

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

.1_1.txz to me. > I'm surely looking forward modularization of LLVM port; rebuilding it > every time becomes a real PITA given that X11 stack requires it. :-( What real reason of requiring llvm for X11? I am about run time depends: # pkg info -r llvm39 llvm39-3.9.1_4: libEGL-13.0

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On Thu, Mar 30, 2017 at 07:26:43PM +0200, Matthew Rezny wrote: > LLVM 3.8 introduced the option to build a shared LLVM library, which is > what Mesa needs for use at runtime (for e.g. compiling shaders), separate > from linking to it. Previous versions only had one option, if th

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

PTIMIZATIONS_FOR_WITH_DEBUG technique >>>> would not change the "WITNESS and INVARIANTS"-like part of the >>>> issue. In fact if WITH_DEBUG= causes the cmake debug-style >>>> llvm40 build ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG might not >>>> make any

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

e "WITNESS and INVARIANTS"-like part of the >>> issue. In fact if WITH_DEBUG= causes the cmake debug-style >>> llvm40 build ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG might not >>> make any difference: separate enforcing of lack of optimization. >>> >>>

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

quot;-like part of the >> issue. In fact if WITH_DEBUG= causes the cmake debug-style >> llvm40 build ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG might not >> make any difference: separate enforcing of lack of optimization. >> >> But just to see wh

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

as a devel/llvm40 update I'll >>> likely rebuild devel/llvm40 without using WITH_DEBUG= . >>> I'm more concerned with the time it takes than with >>> the file system space involved. >> >> In the case of LLVM, enabling debug builds does a LOT more than adding >> symbols. It's much more lik

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 30 Mar 2017, at 19:55, Brooks Davis wrote: > > On Thu, Mar 30, 2017 at 07:26:19PM +0200, Dimitry Andric wrote: ... >> >> As said, this is because of WITH_DEBUG. Don't use that for the llvm >> ports, for now. It will also allow you to build them with much less RAM >> in

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 2017-Mar-30, at 10:55 AM, Brooks Davis wrote: > P.S. Somewhat off topice, but related. FAIR WARNING: the days of > self-hosted 32-bit systems are numbered. Switching to lld from our > ancient BFD linker will probably buy us some time, but I'd be surprised > if you will be able to build

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

like enabling WITNESS and INVARIANTS in your > kernel, except that the performance of the resulting binary is much > worse than a WITNESS kernel (more like 10x slowdown). > > As Dimitry points out, these builds are of questionable value in ports > so garbage collecting the knob m

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

gt; > -rw-r--r-- 1 root wheel27M Feb 28 01:05 llvm37-3.7.1_4.txz > > -rw-r--r-- 1 root wheel 207M Jan 19 18:20 llvm38-3.8.1_5.txz > > -rw-r--r-- 1 root wheel 244M Mar 23 16:42 llvm39-3.9.1_2.txz > > > > Dimitry, do you know what had causes such a hu

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

17M Jan 29 2016 llvm35-3.5.2_1.txz > -rw-r--r-- 1 root wheel18M Mar 7 2016 llvm36-3.6.2_2.txz > -rw-r--r-- 1 root wheel27M Feb 28 01:05 llvm37-3.7.1_4.txz > -rw-r--r-- 1 root wheel 207M Jan 19 18:20 llvm38-3.8.1_5.txz > -rw-r--r-- 1 root wheel 244M Ma

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

heel17M Jan 29 2016 llvm35-3.5.2_1.txz > -rw-r--r-- 1 root wheel18M Mar 7 2016 llvm36-3.6.2_2.txz > -rw-r--r-- 1 root wheel27M Feb 28 01:05 llvm37-3.7.1_4.txz > -rw-r--r-- 1 root wheel 207M Jan 19 18:20 llvm38-3.8.1_5.txz > -rw-r--r-- 1 root wheel 244M M

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

7.1_4.txz -rw-r--r-- 1 root wheel 207M Jan 19 18:20 llvm38-3.8.1_5.txz -rw-r--r-- 1 root wheel 244M Mar 23 16:42 llvm39-3.9.1_2.txz Dimitry, do you know what had causes such a huge bump in 37 -> 38? They take lots of time to build and package. And given that llvm is indirect depende

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 29 Mar 2017, at 17:53, Brooks Davis wrote: > > On Mon, Mar 27, 2017 at 03:25:04AM -0700, Mark Millard wrote: ... >> This is extreme enough that next time I synchronize >> /usr/ports and it has a devel/llvm40 update I'll >> likely rebuild devel/llvm40 without using

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On Mon, Mar 27, 2017 at 03:25:04AM -0700, Mark Millard wrote: > On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: > > > On 26 Mar 2017, at 23:36, Mark Millard wrote: > >> > >> I upgraded from llvm40 r4 to final. An interesting result was > >> its creation

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

, what about space for a local repository when using synth for ports? I could run out of space on some of my partitions but could make a much bigger separate partition if necessary, 500 GB or more. If this question diverges from the proper thread topic, feel free to change the subject line

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 27 Mar 2017, at 23:11, Mark Millard wrote: > > On 2017-Mar-27, at 5:53 AM, Dimitry Andric wrote: >> On 27 Mar 2017, at 12:25, Mark Millard wrote: >>> >>> On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: On 26 Mar 2017, at 23:36, Mark Millard

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 2017-Mar-27, at 5:53 AM, Dimitry Andric wrote: > On 27 Mar 2017, at 12:25, Mark Millard wrote: >> >> On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: >>> On 26 Mar 2017, at 23:36, Mark Millard wrote: > ... Installed packages to be REMOVED:

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 27 Mar 2017, at 12:25, Mark Millard wrote: > > On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: >> On 26 Mar 2017, at 23:36, Mark Millard wrote: ... >>> Installed packages to be REMOVED: >>> llvm40-4.0.0.r4 >>> >>> Number of

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 2017-Mar-27, at 3:25 AM, Mark Millard wrote: > On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: > >> On 26 Mar 2017, at 23:36, Mark Millard wrote: >>> >>> I upgraded from llvm40 r4 to final. An interesting result was >>> its

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: > On 26 Mar 2017, at 23:36, Mark Millard wrote: >> >> I upgraded from llvm40 r4 to final. An interesting result was >> its creation of a backup package for llvm40-4.0.0.r4: >> >> about 13 cpu-core-hours

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 26 Mar 2017, at 23:36, Mark Millard wrote: > > I upgraded from llvm40 r4 to final. An interesting result was > its creation of a backup package for llvm40-4.0.0.r4: > > about 13 cpu-core-hours running pkg create > > (Remember: I've been building with WITH_DEBUG= ) Its >

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

[I add some what-it-take-for-an-upgrade information.] On 2017-Mar-12, at 6:53 PM, Mark Millard <mar...@dsl-only.net> wrote: > Summary: RAM+(peak swap) was about 26 GiBytes. > Also: about 118 GiByte /usr/obj/. . ./llvm40/ area. > (2 processors, 2 cores e

FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

FreeBSD does not report peak swap usage "since boot". So I do not have a cross check on if I missed seeing a higher peak then I report in the details below.] What all this note spans as part of the build: # more /var/db/ports/devel_llvm40/options # This file is auto-generated by 'm

Re: What builds go to snapshots?

On 2016-05-23 10:10, Sergey Manucharian wrote: > Excerpts from Allan Jude's message from Sun 22-May-16 23:55: >> On 2016-05-22 23:33, Sergey Manucharian wrote: >>> Is there any materialistic definition of those builds, which >>> become snapshots at [0]? >>> >>> - Sergey >>> >>> [0]

Re: What builds go to snapshots?

Excerpts from Allan Jude's message from Sun 22-May-16 23:55: > On 2016-05-22 23:33, Sergey Manucharian wrote: > > Is there any materialistic definition of those builds, which > > become snapshots at [0]? > > > > - Sergey > > > > [0] ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/ >

Re: What builds go to snapshots?

On 2016-05-22 23:33, Sergey Manucharian wrote: > Is there any materialistic definition of those builds, which > become snapshots at [0]? > > - Sergey > > [0] ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/ > > ___ >

What builds go to snapshots?

Is there any materialistic definition of those builds, which become snapshots at [0]? - Sergey [0] ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/ ___ freebsd-current@freebsd.org mailing list

So, what I have read and seen

Is that the lot of you have treated a homeless man with disrespect simply because he was open and honest about what goes on in his life. I have also read about his ideas and they make perfect sense to me. Aiding and assisting the blind while standing up for others is not a bad thing. The reaction

Re: What changed in rc.d infrastructure in last months?

On 26 October 2015 at 01:27, Lev Serebryakov wrote: > Hello NGie, > > Sunday, October 25, 2015, 11:09:03 PM, you wrote: > > >> Ok, this is really not making sense from a design perspective. >> `ifconfig_` is being overloaded for starting up hostap’s (even though >> ifconfig

Re: What changed in rc.d infrastructure in last months?

Hello NGie, Sunday, October 25, 2015, 11:09:03 PM, you wrote: > Ok, this is really not making sense from a design perspective. > `ifconfig_` is being overloaded for starting up hostap’s (even though > ifconfig itself doesn’t support hostap — only `wlanmode ap`). I don’t ifconfig doesn't

Re: What changed in rc.d infrastructure in last months?

ld someone please figure out a > cleanish solution to this? I'd really appreciate it. Note that /etc/pccard_ether bails right away if the interface is marked up without doing anything. That is what is supposed to make devd events at boot get ignored. (See the initial loop in pccard_ether_start().

Re: What changed in rc.d infrastructure in last months?

. > > Starting devd. > ifconfig: SIOCS80211: Device busy > hostapd already running? (pid=455). > em1: link state changed to UP > eltel: link state changed to UP > skynet: link state changed to UP > Starting Network: wlan0. > > Before this there was no second

Re: What changed in rc.d infrastructure in last months?

> On Oct 25, 2015, at 12:39, Lev Serebryakov wrote: > > Hello NGie, > > Sunday, October 25, 2015, 10:30:47 PM, you wrote: > > >> This [the hostapd start/stop logic] all gets triggered whenever the >> interface goes up and down. > So, first time hostapd is started by

Re: What changed in rc.d infrastructure in last months?

Hello NGie, Sunday, October 25, 2015, 10:45:10 PM, you wrote: > It depends on how it’s setup. Is your interface is using DHCP and are you > using the stock devd.conf file? From etc/devd.conf: devd.conf is stock one, but, of course, HOSTAP-interface uses static address. One more time:

Re: What changed in rc.d infrastructure in last months?

> On Oct 25, 2015, at 12:54, NGie Cooper wrote: ... > I’ll need to double-check the rcorder and get back to you on that. Answering this part: nope. devd still gets started after netif on my branch, so it’ll still start hostapd twice: $ rcorder `make -VFILES

Re: What changed in rc.d infrastructure in last months?

se `_ifconfig_getargs` could be used to grab the variables from `ifconfig_` — but it seems like a kludge to me). I’d need to boot up FreeBSD on one of my PC laptops to confirm what the behavior is (the earliest I will likely be able to do this is later on today). $ grep -r hostap sbin/ifconfig/ sbin

What changed in rc.d infrastructure in last months?

em0 em1 wlan0 gif0. Starting devd. ifconfig: SIOCS80211: Device busy hostapd already running? (pid=455). em1: link state changed to UP eltel: link state changed to UP skynet: link state changed to UP Starting Network: wlan0. Before this there was no second try to run hostapd. What should I c

Re: What changed in rc.d infrastructure in last months?

ing? (pid=455). > em1: link state changed to UP > eltel: link state changed to UP > skynet: link state changed to UP > Starting Network: wlan0. > > Before this there was no second try to run hostapd. What should I change in > /etc/rc.d to eliminate this double-run and do

Re: What changed in rc.d infrastructure in last months?

Hello NGie, Sunday, October 25, 2015, 10:30:47 PM, you wrote: > This [the hostapd start/stop logic] all gets triggered whenever the interface > goes up and down. So, first time hostapd is started by /etc/rc.d/netif before devd, and second time devd call /etc/rc.d/netif again on interface

Re: What changed in rc.d infrastructure in last months?

> On Oct 25, 2015, at 12:30, NGie Cooper wrote: … > 445 # hostapif if > 446 # Returns 0 if the interface is a HOSTAP interface and 1 otherwise. > 447 hostapif() > 448 { > 449 local _tmpargs _arg > 450 _tmpargs=`_ifconfig_getargs $1` > 451 > 452

Re: What changed in rc.d infrastructure in last months?

Hello NGie, Sunday, October 25, 2015, 10:39:51 PM, you wrote: > It’s documented here: > On the other hand, if you want to configure your wireless > interface with hostapd(8), you need to add ``HOSTAP'' to the > ifconfig_ variable. hostapd(8)

Re: What changed in rc.d infrastructure in last months?

> On Oct 25, 2015, at 12:46, Lev Serebryakov wrote: > > Hello NGie, > > Sunday, October 25, 2015, 10:39:51 PM, you wrote: > > >> It’s documented here: > >> On the other hand, if you want to configure your wireless >> interface with

Re: What to do about RCS/OpenRCS

On Sat, May 09, 2015 at 11:27:57AM -0700, Jos Backus wrote: Maybe off-topic, but functionality-wise it might make much more sense to import Fossil. RCS has too many limitations this day and age when better tools are available. Of course, this would require people to learn something new, which

Re: What to do about RCS/OpenRCS

On May 11, 2015 2:31 AM, Lars Engels lars.eng...@0x20.net wrote: On Sat, May 09, 2015 at 11:27:57AM -0700, Jos Backus wrote: Maybe off-topic, but functionality-wise it might make much more sense to import Fossil. RCS has too many limitations this day and age when better tools are

Re: What to do about RCS/OpenRCS

On Mon, May 11, 2015 at 09:12:57AM -0700, Jos Backus wrote: On May 11, 2015 9:10 AM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Mon, May 11, 2015 at 08:43:06AM -0700, Jos Backus wrote: On May 11, 2015 2:31 AM, Lars Engels lars.eng...@0x20.net wrote: On Sat, May 09, 2015 at

Re: What to do about RCS/OpenRCS

On Mon, 2015-05-11 at 09:27 -0700, Jos Backus wrote: On May 11, 2015 9:21 AM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Mon, May 11, 2015 at 09:12:57AM -0700, Jos Backus wrote: On May 11, 2015 9:10 AM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Mon, May

Re: What to do about RCS/OpenRCS

On May 11, 2015 9:21 AM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Mon, May 11, 2015 at 09:12:57AM -0700, Jos Backus wrote: On May 11, 2015 9:10 AM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Mon, May 11, 2015 at 08:43:06AM -0700, Jos Backus wrote: On May 11,

Re: What to do about RCS/OpenRCS

On Mon, May 11, 2015 at 08:43:06AM -0700, Jos Backus wrote: On May 11, 2015 2:31 AM, Lars Engels lars.eng...@0x20.net wrote: On Sat, May 09, 2015 at 11:27:57AM -0700, Jos Backus wrote: Maybe off-topic, but functionality-wise it might make much more sense to import Fossil. RCS has too

Re: What to do about RCS/OpenRCS

On May 11, 2015 9:33 AM, David Chisnall thera...@freebsd.org wrote: [snip] And now you’re moving beyond missing the point and just trolling. Thanks for the ad hominen, David. You continue to make my point. Over and out, Jos David ___

Re: What to do about RCS/OpenRCS

On 11 May 2015, at 17:27, Jos Backus j...@catnook.com wrote: I didn't miss anything. My point is that debating to update one piece of obsolete software with another is silly, and that FreeBSD should try to move forward in this area. But that's hard, as your response indicates. Steve is

Re: What to do about RCS/OpenRCS

On 05/08/15 15:59, Davide Italiano wrote: On Fri, May 8, 2015 at 1:34 PM, Pedro Giffuni p...@freebsd.org wrote: Hi; I guess I see the following options: 1) Just leave GNU RCS in the tree. 2) Improve OpenRCS so it can be swapped in. 3) Remove RCS dependencies from other parts

Re: What to do about RCS/OpenRCS

On May 9, 2015, at 8:05 AM, Pedro Giffuni p...@freebsd.org wrote: We do that with GNU code anyways. The latest (GPLv3) version of RCS has already diverged and is incompatible for some third party software so we basically ran out of support from upstream. OpenRCS has it's own share of

Re: What to do about RCS/OpenRCS

Maybe off-topic, but functionality-wise it might make much more sense to import Fossil. RCS has too many limitations this day and age when better tools are available. Of course, this would require people to learn something new, which I know can be a challenge. Jos

Re: What to do about RCS/OpenRCS

Hi; On 08/05/2015 10:44 a.m., John Baldwin wrote: On Thursday, May 07, 2015 04:18:38 PM NGie Cooper wrote: On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni p...@freebsd.org wrote: Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't

Re: What to do about RCS/OpenRCS

On Thursday, May 07, 2015 04:18:38 PM NGie Cooper wrote: On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni p...@freebsd.org wrote: Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should

Re: What to do about RCS/OpenRCS

On Fri, May 8, 2015 at 1:34 PM, Pedro Giffuni p...@freebsd.org wrote: Hi; I guess I see the following options: 1) Just leave GNU RCS in the tree. 2) Improve OpenRCS so it can be swapped in. 3) Remove RCS dependencies from other parts of the tree (e.g. etcupdate) and

What to do about RCS/OpenRCS

Hello; Some of you might recall that right before 10.0-Release there was a painful attempt to remove GNU RCS from the base system. From my point of view, the lessons learned from that were: -A lot more people than you might think find it useful to have a small version control system for thing

Re: What to do about RCS/OpenRCS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/07/15 12:09, Pedro Giffuni wrote: Hello; Some of you might recall that right before 10.0-Release there was a painful attempt to remove GNU RCS from the base system. From my point of view, the lessons learned from that were: -A lot

Re: What to do about RCS/OpenRCS

On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should though) so I am not in a good position to take the next step and deal with any fallout it may produce. If we can have a build-knob to disable GNU RCS and enable the new one I will happily

Re: What to do about RCS/OpenRCS

On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni p...@freebsd.org wrote: Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should though) so I am not in a good position to take the next step and

Re: What to do about RCS/OpenRCS

Il giorno 08/mag/2015, alle ore 00:26, Doug Brewer brewer.d...@gmail.com ha scritto: On Thu, May 07, 2015 at 04:18:38PM -0700, NGie Cooper wrote: On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni p...@freebsd.org mailto:p...@freebsd.org wrote: Hello; On 05/07/15 14:56,

Re: What to do about RCS/OpenRCS

On Thu, May 07, 2015 at 04:18:38PM -0700, NGie Cooper wrote: On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni p...@freebsd.org wrote: Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I

Re: What to do about RCS/OpenRCS

Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should though) so I am not in a good position to take the next step and deal with any fallout it may produce. If we can have a build-knob to

Re: What parts of UMA are part of the stable ABI?

I've put the full patch to convert uma_malloc and uma_free to accept a vm_size_t up for review[1]. It ended up being more extensive than expected as a fair number of places do use uma_set_allocf(). I do plan on MFC'ing this patch. This survive a make tinderbox (ignoring some vt-related LINT

Re: What parts of UMA are part of the stable ABI?

On Wednesday, March 18, 2015 12:28:07 PM Adrian Chadd wrote: On 18 March 2015 at 08:23, John Baldwin j...@freebsd.org wrote: On Wednesday, March 18, 2015 11:19:21 AM Ryan Stone wrote: On Wed, Mar 18, 2015 at 10:24 AM, John Baldwin j...@freebsd.org wrote: I do think the normal zone

Re: What parts of UMA are part of the stable ABI?

On Friday, March 13, 2015 07:48:38 PM Ryan Stone wrote: In this freebsd-hackers thread[1], a user reported that 10.1-RELEASE crashes during boot on a system with 3TB of RAM. As it turns out, when you have that much RAM ZFS autotunes itself to allocate a 6GB hash table. This triggers a nasty

Re: What parts of UMA are part of the stable ABI?

On Wed, Mar 18, 2015 at 10:24 AM, John Baldwin j...@freebsd.org wrote: I do think the normal zone callbacks passed to uma_zcreate() are too public to change. Or at least, you would need to do some crazy ABI shim where you have a uma_zcreate_new() that you map to uma_zcreate() via a #define

Re: What parts of UMA are part of the stable ABI?

On Wednesday, March 18, 2015 11:19:21 AM Ryan Stone wrote: On Wed, Mar 18, 2015 at 10:24 AM, John Baldwin j...@freebsd.org wrote: I do think the normal zone callbacks passed to uma_zcreate() are too public to change. Or at least, you would need to do some crazy ABI shim where you have a

Re: What parts of UMA are part of the stable ABI?

On 3/19/15 3:28 AM, Adrian Chadd wrote: On 18 March 2015 at 08:23, John Baldwin j...@freebsd.org wrote: On Wednesday, March 18, 2015 11:19:21 AM Ryan Stone wrote: On Wed, Mar 18, 2015 at 10:24 AM, John Baldwin j...@freebsd.org wrote: I do think the normal zone callbacks passed to

Re: What parts of UMA are part of the stable ABI?

[snip] So yes, I'd like to see this in -HEAD sooner rather than later. You did the great work of chasing it down, so let's get it in -HEAD. :) -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: What parts of UMA are part of the stable ABI?

On 18 March 2015 at 08:23, John Baldwin j...@freebsd.org wrote: On Wednesday, March 18, 2015 11:19:21 AM Ryan Stone wrote: On Wed, Mar 18, 2015 at 10:24 AM, John Baldwin j...@freebsd.org wrote: I do think the normal zone callbacks passed to uma_zcreate() are too public to change. Or at

What parts of UMA are part of the stable ABI?

In this freebsd-hackers thread[1], a user reported that 10.1-RELEASE crashes during boot on a system with 3TB of RAM. As it turns out, when you have that much RAM ZFS autotunes itself to allocate a 6GB hash table. This triggers a nasty 32-bit integer truncation bug in malloc(9). malloc() calls

What replaces DIOCGDINFO?

-r276737 removed 4 ioctls, including DIOCGDINFO, from sys/disklabel.h. The commit log entry says only Remove old ioctl use and support, once and for all. What are users of that mechanism supposed to use instead? A grep in UPDATING for either DIOCGDINFO or ioctl came up empty. BTW I ran

Re: What replaces DIOCGDINFO?

entry says only Remove old ioctl use and support, once and for all. What are users of that mechanism supposed to use instead? A grep in UPDATING for either DIOCGDINFO or ioctl came up empty. BTW I ran into this because it breaks a port I maintain. I do not run CURRENT, and thus have not been

How to read a disklabel (Re: What replaces DIOCGDINFO?)

Andreas Nilsson andrn...@gmail.com wrote: On Sun, Jan 25, 2015 at 9:31 AM, Perry Hutchison per...@pluto.rain.com wrote: -r276737 removed 4 ioctls, including DIOCGDINFO, from sys/disklabel.h. The commit log entry says only Remove old ioctl use and support, once and for all. What

Re: How to read a disklabel (Re: What replaces DIOCGDINFO?)

says only Remove old ioctl use and support, once and for all. What are users of that mechanism supposed to use instead? http://lists.freebsd.org/pipermail/freebsd-current/2015-January/053960.html might have the answer for you. Same symptom, but DIOCGMEDIASIZE is not the solution

Re: What happened to DIOCGDINFO? Fwd: [package - head-amd64-default][misc/e2fsprogs-libblkid] Failed for e2fsprogs-libblkid-1.42.12 in build

)) { ^ 1 error generated. It was removed in r276737. I don't know what replaces it. Ted, I am including a patch against e2fsprogs's maint branch to fix the build on the future FreeBSD 11+ versions. Please apply. Ian, Warner, *, I think I've got a hold

Re: What happened to DIOCGDINFO? Fwd: [package - head-amd64-default][misc/e2fsprogs-libblkid] Failed for e2fsprogs-libblkid-1.42.12 in build

don't know what replaces it. Ted, I am including a patch against e2fsprogs's maint branch to fix the build on the future FreeBSD 11+ versions. Please apply. Ian, Warner, *, I think I've got a hold of this; the replacement appears to be DIOCGMEDIASIZE from sys/disk.h, and has been for more than

What happened to DIOCGDINFO? Fwd: [package - head-amd64-default][misc/e2fsprogs-libblkid] Failed for e2fsprogs-libblkid-1.42.12 in build

Greetings, I am getting new reports of package build failures on head (i386 and amd64 have reported these so far): Ident: $FreeBSD: head/misc/e2fsprogs-libblkid/Makefile 370388 2014-10-07 19:15:52Z mandree $ Log URL:

Re: What happened to DIOCGDINFO? Fwd: [package - head-amd64-default][misc/e2fsprogs-libblkid] Failed for e2fsprogs-libblkid-1.42.12 in build

be the replacement), or is this a temporary failure (inadvertent error)? To the best of my knowledge, and without retrying builds, the package builds fine on 8/9/10. Thanks, Matthias It was removed in r276737. I don't know what replaces it. -- Ian

Re: What is xmmintrin.h, and why aren't ports finding it?

reason that any port wanting to include xmmintrin.h fails to find it? Even though dmesg messages reflects the fact that gcc48 is included within my $PATH? What you have in your PATH does not matter. The xmmintrin.h header contains SSE intrinsics, and should automatically be found by your gcc 4.8

What is xmmintrin.h, and why aren't ports finding it?

Chris H writes: Working on a recent 11-CURRENT install (11-CURRENT #1 amd64 r274134 Nov 5 12:56:14 PST 2014) svn info /usr/ports Revision: 372176 Given the above, and the fact that I have installed lang/gcc-48. Is there any reason that any port wanting to include xmmintrin.h

Re: What is xmmintrin.h, and why aren't ports finding it?

Given the above, and the fact that I have installed lang/gcc-48. Is there any reason that any port wanting to include xmmintrin.h fails to find it? Even though dmesg messages reflects the fact that gcc48 is included within my $PATH? What you have in your PATH does not matter. The xmmintrin.h

What is xmmintrin.h, and why aren't ports finding it?

Greetings, Working on a recent 11-CURRENT install (11-CURRENT #1 amd64 r274134 Nov 5 12:56:14 PST 2014) svn info /usr/ports Revision: 372176 Given the above, and the fact that I have installed lang/gcc-48. Is there any reason that any port wanting to include xmmintrin.h fails to find it? Even

Re: What do you use for kernel debugging?

Hi Daniel, On Thu, 2 Oct 2014 20:50:30 -0400, O'Connor, Daniel wrote [...] I wrote a quick program to dump xHCI extended capabilities https://gist.github.com/DanielO/c42819ae69a1f680039a Cool! Run pciconf -lb and look for the base value for xhciX then run the command with that like so..

Re: What do you use for kernel debugging?

On 1 Oct 2014, at 15:54, O'Connor, Daniel Daniel.O'con...@emc.com wrote: On 1 Oct 2014, at 14:33, Adrian Chadd adr...@freebsd.org wrote: There's also something for XHCI. So I see.. Section 7.6 in here has details..

Re: What do you use for kernel debugging?

On 10/01/14 07:03, Adrian Chadd wrote: There's also something for XHCI. Please please write it for freebsd. :) Hi, The FreeBSD bootloader can run a regular USB stack which connects to the XHCI/EHCI and any supported serial adapter for example. What is currently missing is some PCI pieces

Re: What do you use for kernel debugging?

what percentage of hardware has it hooked up though (the host controller has a designated debug port but it could physically be anything). http://www.coreboot.org/EHCI_Debug_Port The hardware is bit more expensive than a null modem or firewire cable though :( Regards, Daniel

Re: What do you use for kernel debugging?

serial adapter for example. What is currently missing is some PCI pieces to attach the drivers. You don't need the USB debug port to get keyboard/console input. We actually _want_ the debug port support. The EHCI/XHCI debugging stuff is separate from the whole normal USB stack and is really

Re: What do you use for kernel debugging?

in CURRENT via DDB. The kernel does not complete hw probes on my Acer V5. I get stuck on apic_isr looping which leads nowhere. So I thought maybe things improve if I debug from another machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you

Re: What do you use for kernel debugging?

probes on my Acer V5. I get stuck on apic_isr looping which leads nowhere. So I thought maybe things improve if I debug from another machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you agree? I'm on a netbook with no ethernet

Re: What do you use for kernel debugging?

why we don't have it in the tree though it has been done several times in the past). There IS a USB debug standard, Linux has some code to support it. I am not sure what percentage of hardware has it hooked up though (the host controller has a designated debug port but it could physically

Re: What do you use for kernel debugging?

to support it. I am not sure what percentage of hardware has it hooked up though (the host controller has a designated debug port but it could physically be anything). http://www.coreboot.org/EHCI_Debug_Port The hardware is bit more expensive than a null modem or firewire cable though

Re: What do you use for kernel debugging?

, storage). - built one kernel with debug bits and one with release bits (titled them differently of course). - built networking and other components as klds and loaded them at boot. This gave me a quick turnaround time when figuring out what was broken suspend/resume wise. It might help you

What do you use for kernel debugging?

Hello, I am trying to track down a (deadlock?) issue in CURRENT via DDB. The kernel does not complete hw probes on my Acer V5. I get stuck on apic_isr looping which leads nowhere. So I thought maybe things improve if I debug from another machine. What do you use for kernel debugging

Re: What do you use for kernel debugging?

machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you agree? I'm on a netbook with no ethernet and no option for firewire: can I have a USB / nullmodem setup to work? You cannot. I have no old-style uarts hardware anymore

Re: What do you use for kernel debugging?

- Original Message - From: Benjamin Kaduk ka...@mit.edu To: José Pérez Arauzo f...@aoek.com Cc: FreeBSD Current freebsd-current@freebsd.org Sent: Sunday, September 28, 2014 8:54 PM Subject: Re: What do you use for kernel debugging? On Sun, 28 Sep 2014, José Pérez Arauzo wrote: Hello

Re: What do you use for kernel debugging?

debug from another machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you agree? I'm on a netbook with no ethernet and no option for firewire: can I have a USB / nullmodem setup to work? I have no old-style uarts hardware

<    1   2   3   4   5   6   >