i has no 10G interfaces, but if i can help ... i'm using 200Mbit internet,
gigabit intranet, any type of traffic, voip, http etc etc
2007/7/29, OutBackDingo <[EMAIL PROTECTED]>:
>
> Sounds exactly like what we do, multiple queues on bonded high speed
> 10G interfaces
>
>
> On Sat, 28 Jul 2007 16:5
I just DL'ed the latest sources for 6.2 p6. I've compiled
and during the buildworld I get this error. I picked up
the nohup.out at the library area. If you need more info let me
know.
I built 6.2p6 on another machine a week or so ago and had no
problems. I removed all of /usr/obj just in case
Sounds exactly like what we do, multiple queues on bonded high speed
10G interfaces
On Sat, 28 Jul 2007 16:53:36 -0700
"Kip Macy" <[EMAIL PROTECTED]> wrote:
> On 7/28/07, Alexey Karagodov <[EMAIL PROTECTED]> wrote:
> > how can i help you?
>
> I'd like to understand how ALTQ is being used curren
On Saturday 28 July 2007 20:21:02 Peter Jeremy wrote:
> On 2007-Jul-28 19:03:54 -0300, JoaoBR <[EMAIL PROTECTED]> wrote:
> >so using ULE in 7 is ok ? ? ?
>
> Yes.
>
I thought it is SCHED_SMP on 7 ... isn't it? if not forget my joke, I remember
a msg from Roberson saying the _SMP will substitute _
On Sat, Jul 28, 2007 at 05:12:42PM +0400, Andrey V. Elsukov wrote:
> > Am 28.07.2007 um 14:26 schrieb Miroslav Lachman:
> > > If your rc.conf file will start with comment character (#) then
> > > syntax highlight will be OK.
> > WUOUf, that is a pretty trick. Thanks very much. It works.
>
> Also
On Saturday 28 July 2007 10:46:15 Michael Nottebrock wrote:
> >>
> >> Good to hear. Unfortunately my Mobo's BIOS is already up-to-date, the
> >> CPU is officially supported and Cool'n'Quiet works dandy in Windows XP
> >> ... =/
> >
> > my ok msg was too fast, after some time my video starts flicker
On 7/28/07, Alexey Karagodov <[EMAIL PROTECTED]> wrote:
> how can i help you?
I'd like to understand how ALTQ is being used currently. Are there
users using it on high bandwidth interfaces?
As currently implemented it would force serialization, increased
locking overhead, and potentially loss of
how can i help you?
2007/7/29, Kip Macy <[EMAIL PROTECTED]>:
>
> Expanding the net a bit.
>
> -- Forwarded message --
> From: Kip Macy <[EMAIL PROTECTED]>
> Date: Jul 28, 2007 2:03 PM
> Subject: call for ALTQ users
> To: freebsd-net <[EMAIL PROTECTED]>
>
>
> I'm looking at extendin
On 2007-Jul-28 19:03:54 -0300, JoaoBR <[EMAIL PROTECTED]> wrote:
>so using ULE in 7 is ok ? ? ?
Yes.
>ULE in 6.x is absolutely ok and it runs depending on situation faster than
>4BSD with correct kernel and sysctl settings for it and it is perfectly
>stable,
This is simply wrong. ULE in 6.x i
On Saturday 28 July 2007 10:46:15 Michael Nottebrock wrote:
> JoaoBR schrieb:
> > On Saturday 28 July 2007 07:10:21 Michael Nottebrock wrote:
> >> JoaoBR schrieb:
> >>> On Saturday 28 July 2007 04:21:39 Michael Nottebrock wrote:
> JoaoBR schrieb:
> > On Friday 27 July 2007 12:31:55 Nate La
Expanding the net a bit.
-- Forwarded message --
From: Kip Macy <[EMAIL PROTECTED]>
Date: Jul 28, 2007 2:03 PM
Subject: call for ALTQ users
To: freebsd-net <[EMAIL PROTECTED]>
I'm looking at extending ifnet to support multiple tx queues. It
appears that this will inevitably inter
On Saturday 28 July 2007 14:47:17 Kris Kennaway wrote:
> On Sat, Jul 28, 2007 at 03:46:15PM +0200, Michael Nottebrock wrote:
> > Meanwhile I found a workaround for my system: I had SCHED_ULE configured
> > in my kernel - switching to SCHED_4BSD gets rid of the freezes. Should
> > have thought of th
On Sat, Jul 28, 2007 at 11:00:15PM +0200, Michael Nottebrock wrote:
> Kris Kennaway schrieb:
> > On Sat, Jul 28, 2007 at 03:46:15PM +0200, Michael Nottebrock wrote:
> >
> >
> >> Meanwhile I found a workaround for my system: I had SCHED_ULE configured
> >> in my kernel - switching to SCHED_4BSD g
On Sat, 28 Jul 2007, Karl Denninger wrote:
Anyone know if this runs well, poorly,
You'd be better off testing 7-current (which is soon to be 7-stable) with
the SCHED_ULE scheduler in your kernel config, since that's where all the
performance improvements for SMP systems have been going.
ht
On Sat, 28 Jul 2007, Michael Nottebrock wrote:
... and with SCHED_ULE being obsoleted by SCHED_SMP in 7+, it might
actually become the scheduler nobody was ever supposed to be using? It
might still be worthwhile doing some experimenting with powerd and the
different schedulers in -CURRENT, just
Kris Kennaway schrieb:
> On Sat, Jul 28, 2007 at 03:46:15PM +0200, Michael Nottebrock wrote:
>
>
>> Meanwhile I found a workaround for my system: I had SCHED_ULE configured
>> in my kernel - switching to SCHED_4BSD gets rid of the freezes. Should
>> have thought of that sooner, ISTR having probl
At 12:46 PM 7/28/2007, Karl Denninger wrote:
Anyone know if this runs well, poorly, or is asking to unleash the demons of
the Apolcalypse into my computer?
I installed it briefly on a dual xeon quad core before upgrading to
current. It seemed to work just fine.
> dmesg
Copyright (c) 1992-200
Hello Peter,
Thank you for your answer.
2007/7/28, Peter Jeremy <[EMAIL PROTECTED]>:
> On 2007-Jul-27 18:29:44 +0300, Dennis Melentyev <[EMAIL PROTECTED]> wrote:
[skipped architectural description, and, thank for it]
>
> >I'd rather consider this problem as security one.
>
> I think that is a v
On Sat, Jul 28, 2007 at 03:46:15PM +0200, Michael Nottebrock wrote:
> Meanwhile I found a workaround for my system: I had SCHED_ULE configured
> in my kernel - switching to SCHED_4BSD gets rid of the freezes. Should
> have thought of that sooner, ISTR having problems with powerd and
> SCHED_ULE ev
Anyone know if this runs well, poorly, or is asking to unleash the demons of
the Apolcalypse into my computer?
--
--
Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist
http://www.denninger.netMy home on the net - links to everything I do!
http://scubaforum.org
JoaoBR schrieb:
> On Saturday 28 July 2007 07:10:21 Michael Nottebrock wrote:
>
>> JoaoBR schrieb:
>>
>>> On Saturday 28 July 2007 04:21:39 Michael Nottebrock wrote:
>>>
JoaoBR schrieb:
> On Friday 27 July 2007 12:31:55 Nate Lawson wrote:
>
>
> Am 28.07.2007 um 14:26 schrieb Miroslav Lachman:
> > If your rc.conf file will start with comment character (#) then
> > syntax highlight will be OK.
> WUOUf, that is a pretty trick. Thanks very much. It works.
Also you can put in the comment highlight type:
# vim: filetype=sh
--
WBR, Andrey
Michael Worobcuk wrote:
Am 28.07.2007 um 12:55 schrieb Christian Walther:
Hi Michael,
On 28/07/07, Michael Worobcuk <[EMAIL PROTECTED]> wrote:
Hi,
I am using vim-7.1.18.
Everything works fine except the syntax highlighting of rc.conf.
The problem is that vim does no highlighting for the r
Am 28.07.2007 um 14:26 schrieb Miroslav Lachman:
Michael Worobcuk wrote:
Am 28.07.2007 um 12:55 schrieb Christian Walther:
Hi Michael,
On 28/07/07, Michael Worobcuk <[EMAIL PROTECTED]> wrote:
Hi,
I am using vim-7.1.18.
Everything works fine except the syntax highlighting of rc.conf.
The
On Saturday 28 July 2007 08:40:33 Oliver Brandmueller wrote:
> Hi,
>
> On Sat, Jul 28, 2007 at 08:33:55AM -0300, JoaoBR wrote:
> > my ok msg was too fast, after some time my video starts flickering and
> > stays so and the PC is freezed up, disabling powerd and works stable
> >
> > until it freeze
In message <[EMAIL PROTECTED]>, Michael Worobcuk wrote:
>
> I am using vim-7.1.18.
> Everything works fine except the syntax highlighting of rc.conf.
> The problem is that vim does no highlighting for the rc.conf but other
> .conf files are highlighted es expected.
> So I came to the conclusion t
Hi,
On Sat, Jul 28, 2007 at 08:33:55AM -0300, JoaoBR wrote:
> my ok msg was too fast, after some time my video starts flickering and stays
> so and the PC is freezed up, disabling powerd and works stable
>
> until it freeze cpu frequency shifting is done well
>
> manually I can set all cpu spee
On Saturday 28 July 2007 07:10:21 Michael Nottebrock wrote:
> JoaoBR schrieb:
> > On Saturday 28 July 2007 04:21:39 Michael Nottebrock wrote:
> >> JoaoBR schrieb:
> >>> On Friday 27 July 2007 12:31:55 Nate Lawson wrote:
> JoaoBR wrote:
> > Hi
> > when I enable powerd with default flags
Am 28.07.2007 um 12:55 schrieb Christian Walther:
Hi Michael,
On 28/07/07, Michael Worobcuk <[EMAIL PROTECTED]> wrote:
Hi,
I am using vim-7.1.18.
Everything works fine except the syntax highlighting of rc.conf.
The problem is that vim does no highlighting for the rc.conf but
other .conf file
Hi Michael,
On 28/07/07, Michael Worobcuk <[EMAIL PROTECTED]> wrote:
> Hi,
> I am using vim-7.1.18.
> Everything works fine except the syntax highlighting of rc.conf.
> The problem is that vim does no highlighting for the rc.conf but
> other .conf files are highlighted es expected.
> So I came to
Hi,
I am using vim-7.1.18.
Everything works fine except the syntax highlighting of rc.conf.
The problem is that vim does no highlighting for the rc.conf but
other .conf files are highlighted es expected.
So I came to the conclusion that the syntax file for .conf would
probably be ok.
I also t
JoaoBR schrieb:
> On Saturday 28 July 2007 04:21:39 Michael Nottebrock wrote:
>
>> JoaoBR schrieb:
>>
>>> On Friday 27 July 2007 12:31:55 Nate Lawson wrote:
>>>
JoaoBR wrote:
> Hi
> when I enable powerd with default flags (and any other also) the
> comp
On Saturday 28 July 2007 04:21:39 Michael Nottebrock wrote:
> JoaoBR schrieb:
> > On Friday 27 July 2007 12:31:55 Nate Lawson wrote:
> >> JoaoBR wrote:
> >>> Hi
> >>> when I enable powerd with default flags (and any other also) the
> >>> computer freezes some seconds after powerd is started. It doe
JoaoBR schrieb:
> On Friday 27 July 2007 12:31:55 Nate Lawson wrote:
>
>> JoaoBR wrote:
>>
>>> Hi
>>> when I enable powerd with default flags (and any other also) the computer
>>> freezes some seconds after powerd is started. It does not reach login.
>>> Nothing in the logs. This is with am
34 matches
Mail list logo