On Friday, June 22, 2012 6:25:23 am Venkat Duvvuru wrote:
> and no matter in which order I bring up the interfaces, the system becomes
> sluggish after the 5th interface is brought up. So doesn't look like a
> specific driver issue.
Humm. Would it be possible to use KTR_SCHED and capture a ktr du
and no matter in which order I bring up the interfaces, the system becomes
sluggish after the 5th interface is brought up. So doesn't look like a
specific driver issue.
On Fri, Jun 22, 2012 at 2:25 PM, Venkat Duvvuru
wrote:
> This setup has variety of NICs, Intel's, Emulex's and all are stock
> d
This setup has variety of NICs, Intel's, Emulex's and all are stock drivers.
/Venkat
On Thu, Jun 21, 2012 at 7:17 PM, John Baldwin wrote:
> On Thursday, June 21, 2012 8:50:06 am Venkat Duvvuru wrote:
> > While I'm able to ping to the machine..every command on the current
> active
> > session is
On Thursday, June 21, 2012 8:50:06 am Venkat Duvvuru wrote:
> While I'm able to ping to the machine..every command on the current active
> session is sluggish infact doesn't complete, unable to open another ssh
> session..an already opened ssh session doesn't react which is running
> "systat -vmsta
I suspected the hardware hence installed Linux and cross verified that
Linux is working fine.
/Venkat
On Thu, Jun 21, 2012 at 6:20 PM, Venkat Duvvuru
wrote:
> While I'm able to ping to the machine..every command on the current active
> session is sluggish infact doesn't complete, unable to open
While I'm able to ping to the machine..every command on the current active
session is sluggish infact doesn't complete, unable to open another ssh
session..an already opened ssh session doesn't react which is running
"systat -vmstat"...
The only thing I could do is to successfully complete "top -P
On Thursday, June 21, 2012 5:47:48 am Venkat Duvvuru wrote:
> John - Thanks for the reply.
>
> All the CPUs are ~100% idle. I don't see any interrupt storm on any of the
> irqs (vmstat -i).
>
> One observation I made is that I see messages like these in dmesg
>
> ===> mem 0xfaf6-0xfaf7,0
John - Thanks for the reply.
All the CPUs are ~100% idle. I don't see any interrupt storm on any of the
irqs (vmstat -i).
One observation I made is that I see messages like these in dmesg
===> mem 0xfaf6-0xfaf7,0xfaf4-0xfaf5,0xfaf1c000-0xfaf1
irq 40 at device 0.1 on pci6
Loo
On Wednesday, June 20, 2012 6:47:34 am Venkat Duvvuru wrote:
> Hi,
> MSI-x supports upto 2048 vectors but what I see in freebsd 8.2 is that when
> I use more than ~30 vectors, system becomes dead slow.
> Is there a limitation on number of msi vectors that can be used in 8.2?
FreeBSD/x86 supports r
Hi,
MSI-x supports upto 2048 vectors but what I see in freebsd 8.2 is that when
I use more than ~30 vectors, system becomes dead slow.
Is there a limitation on number of msi vectors that can be used in 8.2?
/Venkat
___
freebsd-net@freebsd.org mailing lis
10 matches
Mail list logo