| John Baldwin |
| Nov 8, 7:27 am 2010 |
| Fernando Apesteguía |
| Nov 8, 11:20 am 2010 |
| John Baldwin | Re: [PATCH] mptutil(8) - capture errors and percolate up ...
The explicit 'return (ENOMEM)' calls are fine as-is. I do not think they need
changing.
Having static char arrays of '15' rather than '16' is probably pointless. The
stack is already at least 4-byte aligned on all the architectures we support,
so a 15-byte char array will actually be 16 bytes. It was chose to be a good
enough value, not an exact fit. An exact fit is not important here.
Moving the 'buf' in mpt_raid_level() is a style bug. It should stay where it
is. Same with 'buf' ...
| Nov 8, 7:58 am 2010 |
| Garrett Cooper | Re: [PATCH] mptutil(8) - capture errors and percolate up ...
I'll changed back all of the other *alloc calls (I was just
thinking about all of the other awesome cases that malloc can fail,
but if we break that assumption a lot more of our programs would break
too unfortunately :(...).
I read up on cam_getccb and I agree based on the description today:
"cam_getccb() allocates a CCB using malloc(3) and sets fields in the CCB
header using values from the cam_device structure."
But if it called something else in cam_getccb other ...
| Nov 8, 10:47 am 2010 |
| Alexey Shuvaev | Re: ccache pausing in buildworld
Certainly, I have all these in the host machine and native buildworld
works as expected. What I was talking about is cross-compiling, i.e.:
make TARGET=i386 buildworld
on amd64 host.
BTW, the absence of clang testers on arm architecture would not change
unless the cross-compiling issue with clang is resolved.
Cross-compilation is a MUST HAVE here (there is no other way to bootstrap
the platform).
Alexey.
_______________________________________________
freebsd-hackers@freebsd.org ...
| Nov 8, 11:13 am 2010 |
| Emanuel Haupt |
| Nov 8, 11:50 am 2010 |
| Dimitry Andric | Re: ccache pausing in buildworld
Have you read http://wiki.freebsd.org/BuildingFreeBSDWithClang, which
suggests to put:
.if !defined(CC) || ${CC} == "cc"
CC=clang
.endif
.if !defined(CXX) || ${CXX} == "c++"
CXX=clang++
.endif
# Don't die on warnings
NO_WERROR=
WERROR=
in your /etc/src.conf (or make.conf, depending on your preference)?
If you use that, it should work, at least for the build32 stage of
buildworld on amd64. This workaround is only needed on amd64, not ...
| Nov 8, 11:01 am 2010 |
| Emanuel Haupt |
| Nov 8, 11:42 am 2010 |
| Alexey Shuvaev | Re: ccache pausing in buildworld
Just FYI, you would see exact the same problem if you try to compile
i386 world on amd64-CURRENT with clang:
...
/src/lib/csu/i386-elf/crt1_s.S: Assembler messages:
/src/lib/csu/i386-elf/crt1_s.S:34: Error: suffix or operands invalid for `push'
/src/lib/csu/i386-elf/crt1_s.S:37: Error: `8(%ebp)' is not a valid 64 bit base/index expression
/src/lib/csu/i386-elf/crt1_s.S:38: Error: suffix or operands invalid for `push'
/src/lib/csu/i386-elf/crt1_s.S:39: Error: `4(%ebp)' is not a valid 64 bit ...
| Nov 8, 8:34 am 2010 |
| Emanuel Haupt | Re: ccache pausing in buildworld
I've just updated the ccache port to 3.1.1.
Excerpt from the ChangeLog:
* ccache now falls back to preprocessor mode when a non-regular include file
(device, socket, etc) has been detected so that potential hanging due to
blocking reads is avoided.
* CRC errors are now detected when decompressing compressed files in the
cache.
* Fixed potential object file corruption race on NFS.
* Minor documentation corrections.
* Fixed configure detection of ...
| Nov 8, 6:48 am 2010 |
| Dimitry Andric | Re: ccache pausing in buildworld
This is during the 32-bit build stage on amd64? If so, what will
happen, depends on how you defined CC. Makefile.inc1 defines CC as an
environment variable for a sub-make, using something like:
CC="${CC} -m32 ${LIB32CPUFLAGS} -DCOMPAT_32BIT \
-isystem ${LIB32TMP}/usr/include/ \
-L${LIB32TMP}/usr/lib32 \
-B${LIB32TMP}/usr/lib32"
However, if you either put CC=/usr/local/libexec/ccache/world-cc on the
make command line, or in /etc/src.conf or /etc/make.conf as an
unconditional ...
| Nov 8, 12:04 pm 2010 |
| cronfy | Re: Slow disk access while rsync - what should I tune?
Hello.
That is what surprised me when I did experiment with backups. If I
move backup off from the production server (to another less loaded
production server indeed), server that shuld be backed up starts to
run fine while backups are created. I think it means that problem is
not with vnode/dir caches..
At the other side the server who received backups became very slow. So
the problem looks to be related to writes or file creation/hardlinking
somehow...
At the moment I do not have ...
| Nov 8, 6:57 am 2010 |
| Luigi Rizzo |
| Nov 8, 7:18 am 2010 |
| cronfy |
| Nov 8, 6:47 am 2010 |
| Dmitry Krivenok |
| Nov 8, 6:30 am 2010 |
| Adrian Chadd |
| Nov 8, 5:31 am 2010 |
