Re: FreeBSD FUSE calls truncate() on read-only files

On 2/27/15 7:32 AM, Benjamin Kaduk wrote: On Fri, 27 Feb 2015, Julian Elischer wrote: for example it caches information when it shouldn't, even from 'dynamic' file systems We had to change the code to disable it as our data is synthetic and might change between reads. fstat info is also cached

Re: Massive libxo-zation that breaks everything

On 2 March 2015 at 04:47, Allan Jude wrote: > On 2015-03-01 19:20, Arseny Nasokin wrote: > > On 1 March 2015 at 22:10, Allan Jude wrote: > > > >> On 2015-03-01 13:49, Harrison Grundy wrote: > >>> Thanks! > >>> > >>> That does seem useful, but I'm not sure I see the reasoning behind > >>> putting

Re: Massive libxo-zation that breaks everything

On 3/1/15 10:49 AM, Harrison Grundy wrote: Thanks! That does seem useful, but I'm not sure I see the reasoning behind putting into base, over a port or package, since processing XML in base is a pain, and it can't serve up JSON or HTML without additional utilities anyway. (If I'm reviving a lon

Re: Massive libxo-zation that breaks everything

On 3/1/15 11:10 AM, Allan Jude wrote: On 2015-03-01 13:49, Harrison Grundy wrote: Thanks! That does seem useful, but I'm not sure I see the reasoning behind putting into base, over a port or package, since processing XML in base is a pain, and it can't serve up JSON or HTML without additional u

Re: Massive libxo-zation that breaks everything

On 1 Mar 2015, at 21:29, Rui Paulo wrote: > > On Mar 1, 2015, at 11:11, David Chisnall wrote: >> How would it be in a port? It involves modifying core utilities (some of >> which, like ifconfig, rely on kernel APIs that change between releases) to >> emit structured output. Maintaining two co

Re: Massive libxo-zation that breaks everything

On 2 Mar 2015, at 09:16, Julian Elischer wrote: > > if we develop a suitable post processor with pluggable grammars, we save a > lot of work. > given enough examples you could almost have automatically generated grammars. This decoupled approach is problematic. A large part of the point of lib

r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Buildworld fails in CURRENT r279514 with the following error: [...] - --- sbin.all__D --- - --- camcontrol.o --- cc -O2 -pipe -O3 -O3 -pipe -march=native -std=gnu99 -fstack-protector - -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused

Re: Massive libxo-zation that breaks everything

On 03/02/15 01:23, David Chisnall wrote: > On 1 Mar 2015, at 21:29, Rui Paulo wrote: >> >> On Mar 1, 2015, at 11:11, David Chisnall >> wrote: >>> How would it be in a port? It involves modifying core >>> utilities (some of which, like ifconfig, rely on kernel APIs >>> that change between rele

Re: Massive libxo-zation that breaks everything

On 2 Mar 2015, at 09:24, Harrison Grundy wrote: > > It would seem like the libxo stuff runs the risk of becoming this same > API. Why? The 'API' in the case of an libxo-ised program is a stream on stdout that is then consumed by a JSON or XML parser. XML and JSON are intrinsically extensible

Re: Massive libxo-zation that breaks everything

On 3/2/15 4:25 AM, David Chisnall wrote: On 2 Mar 2015, at 09:16, Julian Elischer wrote: if we develop a suitable post processor with pluggable grammars, we save a lot of work. given enough examples you could almost have automatically generated grammars. This decoupled approach is problemat

Re: Massive libxo-zation that breaks everything

On 3/2/15 4:14 AM, Julian Elischer wrote: On 3/1/15 10:49 AM, Harrison Grundy wrote: Thanks! That does seem useful, but I'm not sure I see the reasoning behind putting into base, over a port or package, since processing XML in base is a pain, and it can't serve up JSON or HTML without additio

Re: r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

Can you post the contents of your make.conf and src.conf? I didn't see this in any of my "make tinderbox" runs ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebs

Re: Massive libxo-zation that breaks everything

On Mon, 2 Mar 2015 09:23:55 + David Chisnall wrote > On 1 Mar 2015, at 21:29, Rui Paulo wrote: > > > > On Mar 1, 2015, at 11:11, David Chisnall wrote: > >> How would it be in a port? It involves modifying core utilities (some of > >> which, like ifconfig, rely on kernel APIs that change b

Re: sa(4) driver changes available for test

> On Mar 1, 2015, at 9:29 PM, Kenneth D. Merry wrote: > > On Sun, Mar 01, 2015 at 19:41:07 -0500, Dan Langille wrote: >> >>> On Mar 1, 2015, at 7:31 PM, Kenneth D. Merry wrote: >>> >>> On Sun, Mar 01, 2015 at 19:15:05 -0500, Dan Langille wrote: > On Feb 17, 2015, at 1:36 PM, Kenneth

Re: sa(4) driver changes available for test

On Mon, Mar 02, 2015 at 11:09:57 -0500, Dan Langille wrote: > > > On Mar 1, 2015, at 9:29 PM, Kenneth D. Merry wrote: > > > > On Sun, Mar 01, 2015 at 19:41:07 -0500, Dan Langille wrote: > >> > >>> On Mar 1, 2015, at 7:31 PM, Kenneth D. Merry wrote: > >>> > >>> On Sun, Mar 01, 2015 at 19:15:05

Re: sa(4) driver changes available for test

> On Mar 2, 2015, at 11:31 AM, Kenneth D. Merry wrote: > > On Mon, Mar 02, 2015 at 11:09:57 -0500, Dan Langille wrote: >> >>> On Mar 1, 2015, at 9:29 PM, Kenneth D. Merry wrote: >>> >>> On Sun, Mar 01, 2015 at 19:41:07 -0500, Dan Langille wrote: > On Mar 1, 2015, at 7:31 PM, Kenneth

Re: sa(4) driver changes available for test

> On Feb 13, 2015, at 7:32 PM, Kenneth D. Merry wrote: > > > I have a fairly large set of changes to the sa(4) driver and mt(1) driver > that I'm planning to commit in the near future. > > A description of the changes is here and below in this message. > > If you have tape hardware and the in

Re: sa(4) driver changes available for test

> On Mar 1, 2015, at 9:06 PM, Kenneth D. Merry wrote: > > On Sun, Mar 01, 2015 at 19:40:40 -0500, Dan Langille wrote: >> >>> On Mar 1, 2015, at 7:36 PM, Kenneth D. Merry wrote: >>> >>> On Sun, Mar 01, 2015 at 19:28:37 -0500, Dan Langille wrote: > On Mar 1, 2015, at 7:18 PM, Kenneth

Re: sa(4) driver changes available for test

On Mon, Mar 02, 2015 at 11:43:15 -0500, Dan Langille wrote: > > > On Mar 1, 2015, at 9:06 PM, Kenneth D. Merry wrote: > > > > On Sun, Mar 01, 2015 at 19:40:40 -0500, Dan Langille wrote: > >> > >>> On Mar 1, 2015, at 7:36 PM, Kenneth D. Merry wrote: > >>> > >>> On Sun, Mar 01, 2015 at 19:28:37

Re: sa(4) driver changes available for test

On Mon, Mar 02, 2015 at 11:44:09 -0500, Dan Langille wrote: > > > On Mar 2, 2015, at 11:31 AM, Kenneth D. Merry wrote: > > > > On Mon, Mar 02, 2015 at 11:09:57 -0500, Dan Langille wrote: > >> > >>> On Mar 1, 2015, at 9:29 PM, Kenneth D. Merry wrote: > >>> > >>> On Sun, Mar 01, 2015 at 19:41:0

Re: sa(4) driver changes available for test

On Mon, Mar 02, 2015 at 11:45:59 -0500, Dan Langille wrote: > > > On Feb 13, 2015, at 7:32 PM, Kenneth D. Merry wrote: > > > > > > I have a fairly large set of changes to the sa(4) driver and mt(1) driver > > that I'm planning to commit in the near future. > > > > A description of the changes

Re: sa(4) driver changes available for test

> On Mar 2, 2015, at 12:28 PM, Kenneth D. Merry wrote: > > On Mon, Mar 02, 2015 at 11:44:09 -0500, Dan Langille wrote: >> >>> On Mar 2, 2015, at 11:31 AM, Kenneth D. Merry wrote: >>> >>> On Mon, Mar 02, 2015 at 11:09:57 -0500, Dan Langille wrote: > On Mar 1, 2015, at 9:29 PM, Kennet

Re: sa(4) driver changes available for test

> On Mar 2, 2015, at 2:07 PM, Dan Langille wrote: > > >> On Mar 2, 2015, at 12:28 PM, Kenneth D. Merry wrote: >> >> On Mon, Mar 02, 2015 at 11:44:09 -0500, Dan Langille wrote: >>> On Mar 2, 2015, at 11:31 AM, Kenneth D. Merry wrote: On Mon, Mar 02, 2015 at 11:09:57 -0500, Da

Re: Massive libxo-zation that breaks everything

On 3/2/15 5:25 AM, Alfred Perlstein wrote: On 3/2/15 4:25 AM, David Chisnall wrote: On 2 Mar 2015, at 09:16, Julian Elischer wrote: if we develop a suitable post processor with pluggable grammars, we save a lot of work. given enough examples you could almost have automatically generated gra

Re: Massive libxo-zation that breaks everything

On 3/2/15 5:27 AM, Alfred Perlstein wrote: On 3/2/15 4:14 AM, Julian Elischer wrote: On 3/1/15 10:49 AM, Harrison Grundy wrote: Thanks! That does seem useful, but I'm not sure I see the reasoning behind putting into base, over a port or package, since processing XML in base is a pain, and

Re: Massive libxo-zation that breaks everything

On 3/2/15 2:53 PM, Julian Elischer wrote: On 3/2/15 5:25 AM, Alfred Perlstein wrote: On 3/2/15 4:25 AM, David Chisnall wrote: On 2 Mar 2015, at 09:16, Julian Elischer wrote: if we develop a suitable post processor with pluggable grammars, we save a lot of work. given enough examples you c

Doing zero-copy stuff in drivers, or "is vm_fault_quick_hold_pages() enough" ?

Hi, gonzo@ committed a fix (r278615) to the videocore driver for the raspberry pi. The fix involved doing an explicit wire of pages that were about to be passed down to the hardware to send to the videobuffer hardware. It turns out that doing vm_fault_quick_hold_pages() wasn't enough - the pages

Re: Massive libxo-zation that breaks everything

On 03/02/15 11:55, Julian Elischer wrote: > On 3/2/15 5:27 AM, Alfred Perlstein wrote: >> >> >> On 3/2/15 4:14 AM, Julian Elischer wrote: >>> On 3/1/15 10:49 AM, Harrison Grundy wrote: Thanks! That does seem useful, but I'm not sure I see the reasoning behind putting into base

Re: sa(4) driver changes available for test

> On Mar 2, 2015, at 2:47 PM, Dan Langille wrote: > > >> On Mar 2, 2015, at 2:07 PM, Dan Langille wrote: >> >> >>> On Mar 2, 2015, at 12:28 PM, Kenneth D. Merry wrote: >>> >>> On Mon, Mar 02, 2015 at 11:44:09 -0500, Dan Langille wrote: > On Mar 2, 2015, at 11:31 AM, Kenneth D. Me

Re: sa(4) driver changes available for test

On Mon, Mar 02, 2015 at 16:34:34 -0500, Dan Langille wrote: > > > On Mar 2, 2015, at 2:47 PM, Dan Langille wrote: > > > > > >> On Mar 2, 2015, at 2:07 PM, Dan Langille wrote: > >> > >> > >>> On Mar 2, 2015, at 12:28 PM, Kenneth D. Merry wrote: > >>> > >>> On Mon, Mar 02, 2015 at 11:44:09 -

Re: Massive libxo-zation that breaks everything

.. we can/should do both. Just make sure the json/html/xml output is versioned, otherwise you're going to end up with /exactly the same problems/ you have with the current format. -adrian ___ freebsd-current@freebsd.org mailing list http://lists.freeb

Re: sa(4) driver changes available for test

> On Mar 2, 2015, at 4:42 PM, Kenneth D. Merry wrote: > > On Mon, Mar 02, 2015 at 16:34:34 -0500, Dan Langille wrote: >> >>> On Mar 2, 2015, at 2:47 PM, Dan Langille wrote: >>> >>> On Mar 2, 2015, at 2:07 PM, Dan Langille wrote: > On Mar 2, 2015, at 12:28 PM, Kenneth D.

Re: Doing zero-copy stuff in drivers, or "is vm_fault_quick_hold_pages() enough" ?

On Mon, Mar 2, 2015 at 12:42 PM, Adrian Chadd wrote: > Hi, > > gonzo@ committed a fix (r278615) to the videocore driver for the > raspberry pi. The fix involved doing an explicit wire of pages that > were about to be passed down to the hardware to send to the > videobuffer hardware. > > It turns o

Re: Massive libxo-zation that breaks everything

On 3/2/15 4:57 PM, Adrian Chadd wrote: .. we can/should do both. Just make sure the json/html/xml output is versioned, otherwise you're going to end up with /exactly the same problems/ you have with the current format. +1 -Alfred ___ freebsd-cur

Re: Doing zero-copy stuff in drivers, or "is vm_fault_quick_hold_pages() enough" ?

On 2 March 2015 at 15:05, K. Macy wrote: > On Mon, Mar 2, 2015 at 12:42 PM, Adrian Chadd wrote: >> Hi, >> >> gonzo@ committed a fix (r278615) to the videocore driver for the >> raspberry pi. The fix involved doing an explicit wire of pages that >> were about to be passed down to the hardware to s

Re: Doing zero-copy stuff in drivers, or "is vm_fault_quick_hold_pages() enough" ?

>> Right above vm_page_hold(): >> /* >> * Keep page from being freed by the page daemon >> * much of the same effect as wiring, except much lower >> * overhead and should be used only for *very* temporary >> * holding ("wiring"). >> */ > > What's the definition of "very temporary holding" ? Wh

Re: Doing zero-copy stuff in drivers, or "is vm_fault_quick_hold_pages() enough" ?

On 2 March 2015 at 16:12, K. Macy wrote: >>> Right above vm_page_hold(): >>> /* >>> * Keep page from being freed by the page daemon >>> * much of the same effect as wiring, except much lower >>> * overhead and should be used only for *very* temporary >>> * holding ("wiring"). >>> */ >> >> Wha

Re: Massive libxo-zation that breaks everything

On 02.03.2015 22:55, Julian Elischer wrote: > On 3/2/15 5:27 AM, Alfred Perlstein wrote: >> >> >> On 3/2/15 4:14 AM, Julian Elischer wrote: >>> On 3/1/15 10:49 AM, Harrison Grundy wrote: Thanks! That does seem useful, but I'm not sure I see the reasoning behind putting into base

Re: Doing zero-copy stuff in drivers, or "is vm_fault_quick_hold_pages() enough" ?

On Mon, Mar 02, 2015 at 04:17:03PM -0800, Adrian Chadd wrote: > On 2 March 2015 at 16:12, K. Macy wrote: > >>> Right above vm_page_hold(): > >>> /* > >>> * Keep page from being freed by the page daemon > >>> * much of the same effect as wiring, except much lower > >>> * overhead and should be u

Re: Doing zero-copy stuff in drivers, or "is vm_fault_quick_hold_pages() enough" ?

On 2 March 2015 at 16:25, Konstantin Belousov wrote: >> Ok, but is there a specific time length that this should be? > Difference between hold and wire is effectively that held pages are > still kept on the page queues, providing potentially uneccessary work > for pagedaemon to find them and skip

Re: Massive libxo-zation that breaks everything

On 2015-03-02 19:22, Andrey Chernov wrote: > On 02.03.2015 22:55, Julian Elischer wrote: >> On 3/2/15 5:27 AM, Alfred Perlstein wrote: >>> >>> >>> On 3/2/15 4:14 AM, Julian Elischer wrote: On 3/1/15 10:49 AM, Harrison Grundy wrote: > Thanks! > > That does seem useful, but I'm not s

Re: Massive libxo-zation that breaks everything

On Mon, Mar 2, 2015 at 3:45 PM, Alfred Perlstein wrote: > > > On 3/2/15 4:57 PM, Adrian Chadd wrote: > >> .. we can/should do both. >> >> Just make sure the json/html/xml output is versioned, otherwise you're >> going to end up with /exactly the same problems/ you have with the >> current format.

Re: Massive libxo-zation that breaks everything

> On Mar 2, 2015, at 4:22 PM, Andrey Chernov wrote: > >> On 02.03.2015 22:55, Julian Elischer wrote: >>> On 3/2/15 5:27 AM, Alfred Perlstein wrote: >>> >>> On 3/2/15 4:14 AM, Julian Elischer wrote: > On 3/1/15 10:49 AM, Harrison Grundy wrote: > Thanks! > > That does seem

Re: Massive libxo-zation that breaks everything

On 03.03.2015 4:30, Alfred Perlstein wrote: > > >> On Mar 2, 2015, at 4:22 PM, Andrey Chernov wrote: >> >>> On 02.03.2015 22:55, Julian Elischer wrote: On 3/2/15 5:27 AM, Alfred Perlstein wrote: > On 3/2/15 4:14 AM, Julian Elischer wrote: >> On 3/1/15 10:49 AM, Harrison Gr

Re: Massive libxo-zation that breaks everything

On 03.03.2015 3:48, Allan Jude wrote: > On 2015-03-02 19:22, Andrey Chernov wrote: >> On 02.03.2015 22:55, Julian Elischer wrote: >>> On 3/2/15 5:27 AM, Alfred Perlstein wrote: On 3/2/15 4:14 AM, Julian Elischer wrote: > On 3/1/15 10:49 AM, Harrison Grundy wrote: >> Thanks! >

Re: Massive libxo-zation that breaks everything

> On Mar 2, 2015, at 5:37 PM, Andrey Chernov wrote: > >> On 03.03.2015 4:30, Alfred Perlstein wrote: >> >> On Mar 2, 2015, at 4:22 PM, Andrey Chernov wrote: > On 02.03.2015 22:55, Julian Elischer wrote: > On 3/2/15 5:27 AM, Alfred Perlstein wrote: > > >>> On

Re: Massive libxo-zation that breaks everything

On 03.03.2015 4:45, Alfred Perlstein wrote: > > >> On Mar 2, 2015, at 5:37 PM, Andrey Chernov wrote: >> >>> On 03.03.2015 4:30, Alfred Perlstein wrote: >>> >>> > On Mar 2, 2015, at 4:22 PM, Andrey Chernov wrote: > >> On 02.03.2015 22:55, Julian Elischer wrote: >> On 3/2/15 5:27

Re: Massive libxo-zation that breaks everything

On Mon, Mar 02, 2015 at 05:30:31PM -0800, Alfred Perlstein wrote: > > Read the library. It doesn't care what output format it needs. > It is up to the translation layer to do it. You could even do > a csv format or most any other structured output format without > changing the userland utils. >

Re: Massive libxo-zation that breaks everything

> On Mar 2, 2015, at 6:27 PM, Andrey Chernov wrote: >> >> >> The responsibility is on you to provide something better, both the >> architecture AND code. So if you want it backed out, then write something >> better. Otherwise step back and let progress happen. > > As it seems you know a lot

Re: Massive libxo-zation that breaks everything

On 3/2/15 5:30 PM, Alfred Perlstein wrote: On Mar 2, 2015, at 4:22 PM, Andrey Chernov wrote: On 02.03.2015 22:55, Julian Elischer wrote: On 3/2/15 5:27 AM, Alfred Perlstein wrote: On 3/2/15 4:14 AM, Julian Elischer wrote: On 3/1/15 10:49 AM, Harrison Grundy wrote: Thanks! That does see

Re: Massive libxo-zation that breaks everything

> On Mar 2, 2015, at 7:14 PM, Julian Elischer wrote: > >> On 3/2/15 5:30 PM, Alfred Perlstein wrote: >> On Mar 2, 2015, at 4:22 PM, Andrey Chernov wrote: > On 02.03.2015 22:55, Julian Elischer wrote: > On 3/2/15 5:27 AM, Alfred Perlstein wrote: > > >>> On 3/2/

Jenkins build became unstable: FreeBSD_HEAD-tests2 #798

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

nvidia+HEAD amd64 trouble

Hi, I have Lenovo IdeaPad z400 touch laptop. It have GeForce GT 635M graphics card. Also it have integrated Intel card agp0: on vgapci0 agp0: aperture size is 256M, detected 65532k stolen memory when I enable nvidia on laptop bios and trying to use it I got following panic: NVRM: failed to co

Jenkins build is back to stable : FreeBSD_HEAD-tests2 #799

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"