Re: FreeBSD elf_machine_id

2018-08-12 Thread Shane Ambler
On 12/8/18 11:32 pm, blubee blubeeme wrote: > On Sun, Aug 12, 2018 at 9:59 PM blubee blubeeme wrote: > >> >> >> On Sun, Aug 12, 2018 at 7:43 PM Dimitry Andric wrote: >> >>> On 12 Aug 2018, at 13:21, blubee blubeeme wrote: What's the elf_machine_id for FreeBSD amd64 systems?

Re: kernel build failure

2018-08-12 Thread Warner Losh
On Sun, Aug 12, 2018, 4:27 PM Matthew Macy wrote: > > > On Sun, Aug 12, 2018 at 3:25 PM Warner Losh wrote: > >> >> >> On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote: >> >>> Sorry guys, last time I touched ZFS I tried to push to make it an option >>> to >>> statically link and was actually

Re: kernel build failure

2018-08-12 Thread Matthew Macy
On Sun, Aug 12, 2018 at 3:25 PM Warner Losh wrote: > > > On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote: > >> Sorry guys, last time I touched ZFS I tried to push to make it an option >> to >> statically link and was actually told that it wasn't something anyone else >> wanted. The issue comes

Re: kernel build failure

2018-08-12 Thread Warner Losh
On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote: > Sorry guys, last time I touched ZFS I tried to push to make it an option to > statically link and was actually told that it wasn't something anyone else > wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. > LINT is

Re: kernel build failure

2018-08-12 Thread Matthew Macy
Sorry guys, last time I touched ZFS I tried to push to make it an option to statically link and was actually told that it wasn't something anyone else wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. -M On Sun, Aug 12, 2018 at 12:46 PM Trond Endrestøl <

Re: kernel build failure

2018-08-12 Thread Trond Endrestøl
On Sun, 12 Aug 2018 16:51+0200, Trond Endrestøl wrote: > On Sun, 12 Aug 2018 09:37-0400, Michael Butler wrote: > > > Is anyone else seeing this when building a new kernel with ZFS compiled in? > > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o > > Building

Re: TCP server app performance

2018-08-12 Thread Matthias Apitz
El día domingo, agosto 12, 2018 a las 09:32:28p. m. +0200, Michio Honda escribió: > Hi Rozhuk, > > I only use a single CPU core and thread, so SO_REUSEPORT_LB has no > effect. Also, I already accept() in loop until getting error, but this > is not a point as I use persistent TCP

Re: TCP server app performance

2018-08-12 Thread Michio Honda
Hi Rozhuk, I only use a single CPU core and thread, so SO_REUSEPORT_LB has no effect. Also, I already accept() in loop until getting error, but this is not a point as I use persistent TCP connections... Cheers, - Michio On 08/12/2018 07:50 PM, Rozhuk Ivan wrote: On Sun, 12 Aug 2018

RE: zpool scrub. Wtf?

2018-08-12 Thread Cy Schubert
I haven't looked at it closely but from what I saw it was counting scan reads and issued reads. It may be a simple matter of dividing by 2. --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The

Re: TCP server app performance

2018-08-12 Thread Rozhuk Ivan
On Sun, 12 Aug 2018 18:50:17 +0200 Honda Michio wrote: > I'm measuring TCP server app performance using my toy web server. > It just accept TCP connections and responds back HTTP OK to the > clients. It monitors sockets using kqueue, and processes each ready > descriptor using a pair of read()

Re: TCP server app performance

2018-08-12 Thread Rozhuk Ivan
On Sun, 12 Aug 2018 18:50:17 +0200 Honda Michio wrote: > I'm measuring TCP server app performance using my toy web server. > It just accept TCP connections and responds back HTTP OK to the > clients. It monitors sockets using kqueue, and processes each ready > descriptor using a pair of read()

TCP server app performance

2018-08-12 Thread Honda Michio
Hi, I'm measuring TCP server app performance using my toy web server. It just accept TCP connections and responds back HTTP OK to the clients. It monitors sockets using kqueue, and processes each ready descriptor using a pair of read() and write(). (in more detail, it's

Re: zpool scrub. Wtf?

2018-08-12 Thread Shawn Webb
On Tue, Aug 07, 2018 at 10:50:13PM +0700, Alex V. Petrov wrote: > # zpool status > pool: zroot > state: ONLINE > scan: scrub in progress since Tue Aug 7 21:21:51 2018 > 804G scanned at 163M/s, 1,06T issued at 219M/s, 834G total > 0 repaired, 129,87% done, 929637 days 13:43:01

Problem with lastest version of indent

2018-08-12 Thread Michael Tuexen
Dear all, the up-to-date indent translates a line like bla._blub = 1; into a line like bla._ blub = 1; (insert whitespace after _) which breaks C code... Older versions didn't do that Is this change intended? If yes, is there a command line option to turn it off? Best regards Michael

Re: kernel build failure

2018-08-12 Thread Trond Endrestøl
On Sun, 12 Aug 2018 09:37-0400, Michael Butler wrote: > Is anyone else seeing this when building a new kernel with ZFS compiled in? > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel > --- kernel --- > linking kernel > ld: error:

Re: FreeBSD elf_machine_id

2018-08-12 Thread blubee blubeeme
On Sun, Aug 12, 2018 at 9:59 PM blubee blubeeme wrote: > > > On Sun, Aug 12, 2018 at 7:43 PM Dimitry Andric wrote: > >> On 12 Aug 2018, at 13:21, blubee blubeeme wrote: >> > >> > What's the elf_machine_id for FreeBSD amd64 systems? >> > >> > How can I find this info? >> >> There isn't any

Re: FreeBSD elf_machine_id

2018-08-12 Thread blubee blubeeme
On Sun, Aug 12, 2018 at 7:43 PM Dimitry Andric wrote: > On 12 Aug 2018, at 13:21, blubee blubeeme wrote: > > > > What's the elf_machine_id for FreeBSD amd64 systems? > > > > How can I find this info? > > There isn't any FreeBSD-specific machine ID, just a machine ID for > x86-64 (aka amd64) in

kernel build failure

2018-08-12 Thread Michael Butler
Is anyone else seeing this when building a new kernel with ZFS compiled in? Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel --- kernel --- linking kernel ld: error: undefined symbol: dbuf_stats_init >>> referenced by dbuf.c >>>

Re: ffs_truncate3 panics

2018-08-12 Thread Rick Macklem
Konstantin Belousov wrote: [stuff snipped] >Problem with this buffer is that BX_ALTDATA bit is not set. >This is the reason why vinvalbuf(V_ALT) skips it. [more stuff snipped] >The vnode is exclusively locked. Other thread must not be able to >instantiate a buffer under us. That's what I thought,

Re: FreeBSD elf_machine_id

2018-08-12 Thread Dimitry Andric
On 12 Aug 2018, at 13:21, blubee blubeeme wrote: > > What's the elf_machine_id for FreeBSD amd64 systems? > > How can I find this info? There isn't any FreeBSD-specific machine ID, just a machine ID for x86-64 (aka amd64) in general: $ grep x86-64 /usr/include/sys/elf_common.h #define

Re: FreeBSD elf_machine_id

2018-08-12 Thread Gary Jennejohn
On Sun, 12 Aug 2018 13:38:39 +0200 Gary Jennejohn wrote: > On Sun, 12 Aug 2018 19:21:16 +0800 > blubee blubeeme wrote: > > > What's the elf_machine_id for FreeBSD amd64 systems? > > > > How can I find this info? > > > > elfdump -a /bin/ls | grep machine > Oops! In case you don't any

Re: FreeBSD elf_machine_id

2018-08-12 Thread Gary Jennejohn
On Sun, 12 Aug 2018 19:21:16 +0800 blubee blubeeme wrote: > What's the elf_machine_id for FreeBSD amd64 systems? > > How can I find this info? > elfdump -a /bin/ls | grep machine -- Gary Jennejohn ___ freebsd-current@freebsd.org mailing list

FreeBSD elf_machine_id

2018-08-12 Thread blubee blubeeme
What's the elf_machine_id for FreeBSD amd64 systems? How can I find this info? Best, Owen ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to