Alexander Motin writes:
> I haven't dug really deep into current ataraid(4), but AFAIK it is all
> done in software. At least there is no any offloading support on the
> controller drivers level. None of ata(4) drivers do anything except
> executing one ATA command at a time.
Correct.
That doesn
On Saturday 17 April 2010 03:08:18 Roman Divacky wrote:
> Hi,
>
> ClangBSD is a branch of FreeBSD that aims at integrating clang
> (clang.llvm.org) into FreeBSD, replacing GCC as a system compiler.
>
> Recently, we've achieved the state when clang can compile all of FreeBSD
> world on i386/amd64
On Wed, 2010-04-28 at 10:27 +0400, Alex Keda wrote:
> 27.04.2010 18:13, Robert Noland пишет:
> >
> >
> > Alex Keda wrote:
> >> 27.04.2010 17:55, Robert Noland пишет:
> >>>
> >>>
> >>> Alex Keda wrote:
> Following recent changes in dri, xorg server freezes after 20-30
> seconds of work. m
According to Dima Panov:
> while building lang/ruby18:
Which options to you use?
_OPTIONS_READ=ruby+oniguruma-1.8.7.248_1,1
WITHOUT_ONIGURUMA=true
WITH_RDOC=true
WITHOUT_DEBUG=true
I notice your ruby is compiling w/o any -On, try with -O at least?
> clang -I/usr/include -pipe -g -g -std=gnu89
According to Brooks Davis:
> For the foreseeable future, doing anything but using the latest port is a
> recipe for problems.
The "make BOOTSTRAP=yes makesum" is a wonderful trick, thanks Brooks!
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr
In memoriam to Ond
Hi.
I'm glad to present new driver (mvs) for several series of Marvell SATA
controllers (PCI-X, PCIe and SoC-integrated), to work with CAM ATA
infrastructure.
Driver supports following Marvell chips:
Gen-I (SATA 1.5Gbps):
88SX5040, 88SX5041, 88SX5080, 88SX5081
Gen-II (SATA 3Gbps, NCQ, PMP):
Hello!
I have a trouble with my FreeBSD-CURRENT virtual machine running on VmWare
ESX server.
uname -a prints:
FreeBSD host 9.0-CURRENT FreeBSD 9.0-CURRENT #16 r207299: Wed Apr 28
04:15:07 UTC 2010 r...@host:/usr/obj/usr/src/sys/GENERIC amd64
The problem lies in that FreeBSD hangs after "re
On Wednesday 28 April 2010 23:16:38 Ollivier Robert wrote:
> According to Dima Panov:
> > while building lang/ruby18:
> Which options to you use?
>
> _OPTIONS_READ=ruby+oniguruma-1.8.7.248_1,1
> WITHOUT_ONIGURUMA=true
> WITH_RDOC=true
> WITHOUT_DEBUG=true
>
> I notice your ruby is compiling w/o a
I was recently working on the enhanced coredumps
internal to Juniper and realized that there were
some defects in the code I pushed (mostly due to
mismerge), can someone please review?
1) don't allocate hostname[] on the stack
2) don't leak the temp buffer in imgact_elf_coredump.
thank you,
-Alf
On Tue, Apr 27, 2010 at 7:06 PM, Maxim Sobolev wrote:
> Alexander Sack wrote:
>>
>> On Tue, Apr 27, 2010 at 5:25 PM, John Baldwin wrote:
>>>
>>> On Tuesday 27 April 2010 5:06:37 pm Maxim Sobolev wrote:
John Baldwin wrote:
>
> On Tuesday 27 April 2010 4:26:09 pm Maxim Sobolev wro
On Thu, 22 Apr 2010, krad wrote:
> On 22 April 2010 08:33, Alex Keda wrote:
>
> > 22.04.2010 11:29, Gordon Tetlow ?:
> >
> >> On Thu, Apr 22, 2010 at 12:17 AM, Alex Keda >> ad...@lissyara.su>> wrote:
> >>
> >>It's need feature. I test patch - it work for me (CURRENT, amd64)
> >>Can
Hello, Dag-Erling.
You wrote 27 апреля 2010 г., 17:34:14:
> Most pseudo-raid kit has nifty features like checksum offloading,
> composite writes etc.
Why are they called ``PSEUDO-raids'' then?
--
// Black Lion AKA Lev Serebryakov
___
freebsd-current
Lev Serebryakov writes:
> "Dag-Erling Smørgrav" writes:
> > Most pseudo-raid kit has nifty features like checksum offloading,
> > composite writes etc.
> Why are they called ``PSEUDO-raids'' then?
Several reasons - they don't present the array to the OS as a single
device, they don't handle fai
On Thu, Apr 29, 2010 at 02:40:24AM +1100, Dima Panov wrote:
> On Wednesday 28 April 2010 23:16:38 Ollivier Robert wrote:
> > According to Dima Panov:
> > > while building lang/ruby18:
> > Which options to you use?
> >
> > _OPTIONS_READ=ruby+oniguruma-1.8.7.248_1,1
> > WITHOUT_ONIGURUMA=true
> > WI
On Wed, Apr 28, 2010 at 10:32:41PM +0200, Alexey Shuvaev wrote:
> On Thu, Apr 29, 2010 at 02:40:24AM +1100, Dima Panov wrote:
> > On Wednesday 28 April 2010 23:16:38 Ollivier Robert wrote:
> > > According to Dima Panov:
> > > > while building lang/ruby18:
> > > Which options to you use?
> > >
> >
It looks to me like taskqueue_drain(taskqueue_thread, foo) will not
correctly detect whether or not a task is currently running. The check
is against a field in the taskqueue struct, but for the taskqueue_thread
queue with more than one thread, multiple threads can simultaneously be
running a task
FreeBSD bigback.housenet.jrv 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r206111:
Mon Apr 26 01:13:00 CDT 2010
r...@bigback.housenet.jrv:/usr/obj/usr/src/sys/GENERIC amd64
svn 206111 is April 2
system is a Core i7 975 (3.33 GHz x 4 cores 3x threads per core) with 12
GB of RAM, a 2x2TB ZFS boot pool a
Do you have vm.kmem_size set in /boot/loader.conf?
If not, do set it to about double of your physical RAM size. Defaults
are way too conservative for use with large amounts of memory and ZFS.
--Artem
On Wed, Apr 28, 2010 at 8:07 PM, James R. Van Artsdalen
wrote:
> FreeBSD bigback.housenet.jrv
On Wed, Apr 28, 2010 at 8:07 PM, James R. Van Artsdalen
wrote:
> FreeBSD bigback.housenet.jrv 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r206111:
> Mon Apr 26 01:13:00 CDT 2010
> r...@bigback.housenet.jrv:/usr/obj/usr/src/sys/GENERIC ?amd64
>
> svn 206111 is April 2
>
> system is a Core i7 97
19 matches
Mail list logo
