Pawel Jakub Dawidek writes:
> I'd like to give you ZFS v28 for testing. If you are neither brave nor
> mad, you can stop here.
[...]
> So test whatever you can and report back. Look for regressions, strange
> behaviour, missing features, deadlocks, livelocks, preformance
> degradation, etc.
[...]
Cool, but i may try this on a VM and maybe try this on a expermential
production system after I test it on VM since a real system may help
the progress of the new ZFS sinc
On Tue, Aug 31, 2010 at 8:09 PM, Zhu Han wrote:
> That's cool. Thank you for your work on it.
>
> best regards,
> hanzhu
>
>
That's cool. Thank you for your work on it.
best regards,
hanzhu
On Wed, Sep 1, 2010 at 5:59 AM, Pawel Jakub Dawidek wrote:
> Hello.
>
> I'd like to give you ZFS v28 for testing. If you are neither brave nor
> mad, you can stop here.
>
> The patchset is very experimental. It can eat your cooki
Infiniband is currently being worked on, sponsored by Panasas, Isilon
and someone else. It's coming along pretty well.
http://www.h-online.com/open/news/item/ZFS-as-a-Linux-kernel-module-1069056.html
Too bad FreeBSD still lacks Infiniband support. Currently we use ZFS
on FreeBSD and Infin
Pawel,
Pawel Jakub Dawidek wrote:
I'd like to give you ZFS v28 for testing. If you are neither brave nor
mad, you can stop here.
The patchset is very experimental. It can eat your cookie and hurt your
teddy bear, so be warned. Don't try it for anything except testing.
Thank you very much - now
Hi,
I just upgraded from r210042 to r212073 and keep getting the panic
introduced in r211317:
panic: tcp_output: len <= tso_segsz
db:0:kdb.enter.default> bt
Tracing pid 12 tid 100063 td 0xff001881b000
kdb_enter() at kdb_enter+0x3d
panic() at panic+0x1c8
tcp_output() at tcp_output+0x1445
tcp
This is awesome. Thank you!
-J
On Tue, Aug 31, 2010 at 3:59 PM, Pawel Jakub Dawidek wrote:
> Hello.
>
> I'd like to give you ZFS v28 for testing. If you are neither brave nor
> mad, you can stop here.
>
> The patchset is very experimental. It can eat your cookie and hurt your
> teddy bear, so be
On 1 September 2010 10:21, Rui Paulo wrote:
> Hi,
> The DTrace userland project is near completion and you can start using parts
> of it right away (only on FreeBSD HEAD right now).
>
> For more information on how to use DTrace with userland, please read:
> http://wiki.freebsd.org/DTrace/userland
On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek wrote:
> Hello.
>
> I'd like to give you ZFS v28 for testing. If you are neither brave nor
> mad, you can stop here.
Woohoo! Thanks for all your hard work on this!
Matt
___
freebsd-current@freebsd.or
Hi,
The DTrace userland project is near completion and you can start using parts of
it right away (only on FreeBSD HEAD right now).
For more information on how to use DTrace with userland, please read:
http://wiki.freebsd.org/DTrace/userland
This project is being sponsored by the FreeBSD Foundat
Hello.
I'd like to give you ZFS v28 for testing. If you are neither brave nor
mad, you can stop here.
The patchset is very experimental. It can eat your cookie and hurt your
teddy bear, so be warned. Don't try it for anything except testing.
This patchset is also a message we, as the FreeBSD pro
Jilles Tjoelker writes:
> On Wed, Jun 16, 2010 at 10:04:16PM +0300, Jaakko Heinonen wrote:
>> On 2010-06-15, Gabor Kovesdan wrote:
>> > - The iconv.h header files is supposed to be compatible with the GNU
>> > version, i.e. sources should build with base iconv.h and GNU libiconv.
>> > I've just
Gary Jennejohn wrote:
> On Mon, 30 Aug 2010 13:07:38 +0300
> Alexander Motin wrote:
>> Yes, as I have said, at this moment empty ticks skipped only while CPU
>> is in C2/C3 states. In C1 state there is no way to handle lost events on
>> wake up. While it may be not very dangerous, it is not very g
On Tue, Aug 31, 2010 at 10:16 AM, wrote:
> I recorded the stack any time ts->ts_cpu was set and when a thread was
> migrated by sched_switch() I printed out the recorded info. Here's
> what I found:
>
>
> XXX bug 67957: moving 0xff003ff9b800 from 3 to 1
> [1]: pin 0 state 4 move 3 -> 1 done
I recorded the stack any time ts->ts_cpu was set and when a thread was
migrated by sched_switch() I printed out the recorded info. Here's
what I found:
XXX bug 67957: moving 0xff003ff9b800 from 3 to 1
[1]: pin 0 state 4 move 3 -> 1 done by 0xff000cc44000:
#0 0x802b36b4 at bug6795
On Tue, Aug 31, 2010 at 3:48 AM, Alexander Motin wrote:
> Gary Jennejohn wrote:
>> On Mon, 30 Aug 2010 12:11:48 +0200
>> Gary Jennejohn wrote:
>>
>>> On Mon, 30 Aug 2010 13:07:38 +0300
>>> Alexander Motin wrote:
>>>
Gary Jennejohn wrote:
> Hmm. I applied your patches and am now running
On Monday, August 30, 2010 6:22:10 pm Xin LI wrote:
> On 2010/08/27 06:34, John Baldwin wrote:
> > On Thursday, August 26, 2010 8:50:01 pm Xin LI wrote:
> >> Hi,
> >>
> >> The attached patch changes FreeBSD/x86 back to FreeBSD/i386 on i386 and
> >> FreeBSD/amd64 on amd64.
> >>
> >> Comments welcome
On Monday, August 30, 2010 5:53:43 pm Andriy Gapon wrote:
> on 30/08/2010 20:18 Mike Tancsa said the following:
> > At 12:51 PM 8/30/2010, Olivier Smedts wrote:
> >
> >> By any chance, is it disabled in BIOS ?
> >
> > Hi,
> > There are a couple of options in the BIOS. There is a "reboot the box i
Gary Jennejohn wrote:
> On Mon, 30 Aug 2010 12:11:48 +0200
> Gary Jennejohn wrote:
>
>> On Mon, 30 Aug 2010 13:07:38 +0300
>> Alexander Motin wrote:
>>
>>> Gary Jennejohn wrote:
Hmm. I applied your patches and am now running the new kernel. But I
only installed the new kernel and did
On Mon, 30 Aug 2010 12:11:48 +0200
Gary Jennejohn wrote:
> On Mon, 30 Aug 2010 13:07:38 +0300
> Alexander Motin wrote:
>
> > Gary Jennejohn wrote:
> > > Hmm. I applied your patches and am now running the new kernel. But I
> > > only installed the new kernel and didn't do make buildworld insta
Alexander Motin wrote:
> YAMAMOTO, Taku wrote:
>> On Mon, 30 Aug 2010 13:07:38 +0300
>> Alexander Motin wrote:
>>> Gary Jennejohn wrote:
>> (snip)
So, what else did you do to reduce interrupts so much?
Ah, I think I see it now. My desktop has only C1 enabled. Is that it?
Unfo
21 matches
Mail list logo
