-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Nawfal,
Nawfal bin Mohmad Rouyan wrote:
I have been using a Dell machine with 2 bce interfaces as a bridge
between my LAN and Firewall to shape the traffic. Since after the
update, the machine can only run for a few minutes and after
On Mon, 2008-12-15 at 11:47 -0500, Mike Jakubik wrote:
On Sun, December 14, 2008 4:57 am, Xin LI wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Jakubik wrote:
On Mon, December 8, 2008 5:22 pm, Mike Jakubik wrote:
On Mon, December 8, 2008 5:12 pm, Xin LI wrote:
Which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Nawfal,
Nawfal bin Mohmad Rouyan wrote:
I have been using a Dell machine with 2 bce interfaces as a bridge
between my LAN and Firewall to shape the traffic. Since after the
update, the machine can only run for a few minutes and after that no
On Sun, December 14, 2008 4:57 am, Xin LI wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Jakubik wrote:
On Mon, December 8, 2008 5:22 pm, Mike Jakubik wrote:
On Mon, December 8, 2008 5:12 pm, Xin LI wrote:
Which version are you currently using? My previous commit only fixes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Jakubik wrote:
On Mon, December 8, 2008 5:22 pm, Mike Jakubik wrote:
On Mon, December 8, 2008 5:12 pm, Xin LI wrote:
Which version are you currently using? My previous commit only fixes
the excessive interrupt issue, I think this could be a
On Mon, December 8, 2008 5:22 pm, Mike Jakubik wrote:
On Mon, December 8, 2008 5:12 pm, Xin LI wrote:
Which version are you currently using? My previous commit only fixes
the excessive interrupt issue, I think this could be a different
problem, I'm taking a look at the code to see if I can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Jakubik wrote:
On Mon, December 8, 2008 5:22 pm, Mike Jakubik wrote:
On Mon, December 8, 2008 5:12 pm, Xin LI wrote:
Which version are you currently using? My previous commit only fixes
the excessive interrupt issue, I think this could be a
This patch committed fixes the issue reported earlier with interruptions
but there is one more problem discussed here:
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-11/msg00144.html
We also have observed similar bad behavior for network (especially
ssl-based) operations: imaps,
On Mon, December 8, 2008 4:29 am, Oleg Gorokhov wrote:
This patch committed fixes the issue reported earlier with interruptions
but there is one more problem discussed here:
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-11/msg00144.html
We also have observed similar bad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Jakubik wrote:
On Mon, December 8, 2008 4:29 am, Oleg Gorokhov wrote:
This patch committed fixes the issue reported earlier with interruptions
but there is one more problem discussed here:
On Mon, December 8, 2008 5:12 pm, Xin LI wrote:
Which version are you currently using? My previous commit only fixes
the excessive interrupt issue, I think this could be a different
problem, I'm taking a look at the code to see if I can have something
for you.
I was running on the version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI, I have committed the patch as r185653 (stable/7) and r185654
(releng/7.1) so new build would get this issue fixed. Thanks goes to
David who gave review for the changes and all who tested the earlier
patches.
Cheers,
- --
Xin LI [EMAIL
On Tue, Dec 02, 2008 at 04:44:46PM -0800, Xin LI wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi guys,
I think I got a real fix.
I tried that patch with very recent 7-STABLE.
I does fix the problem for me.
Thanks a lot!
Cheers,
- --
Xin LI [EMAIL PROTECTED]
On Wed, December 3, 2008 3:27 am, Dmitry Sivachenko wrote:
On Tue, Dec 02, 2008 at 04:44:46PM -0800, Xin LI wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi guys,
I think I got a real fix.
I tried that patch with very recent 7-STABLE.
I does fix the problem for me.
Good to
Xin LI a écrit :
Hi guys,
I think I got a real fix.
It seems to work for me® too
Server under normal charge (smtp/imap/Maildir for ~1000 users, NFS
filer), everything seems ok... (1h uptime for now)
Thank you !
--
geoffroy desvernay
signature.asc
Description: OpenPGP digital signature
Since last upgrade, I see much more CPU time eated by interrupts (at
least 10% cpu in top)
(see http://dgeo.perso.ec-marseille.fr/cpu-week.png)
The server behave correctly (Or seems to…), and high interrupt number
seems to come from bce cards (source: systat -vmstat)
I just upgraded from
On Tue, December 2, 2008 4:57 am, Geoffroy Desvernay wrote:
Since last upgrade, I see much more CPU time eated by interrupts (at
least 10% cpu in top)
(see http://dgeo.perso.ec-marseille.fr/cpu-week.png)
I am also seeing the same behavior on a farm of Dell servers.
[EMAIL PROTECTED]:~# vmstat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can anyone try reverting the changeset itself? There are two recent
changesets:
http://www.delphij.net/bce-185161.diff.bz2
http://www.delphij.net/bce-184826.diff.bz2
You can revert the change by doing this:
cd /usr/src
fetch
On Tue, December 2, 2008 1:17 pm, Xin LI wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can anyone try reverting the changeset itself? There are two recent
changesets:
http://www.delphij.net/bce-185161.diff.bz2
http://www.delphij.net/bce-184826.diff.bz2
Thanks for the
Xin LI a écrit :
Can anyone try reverting the changeset itself? There are two recent
changesets:
http://www.delphij.net/bce-185161.diff.bz2
http://www.delphij.net/bce-184826.diff.bz2
You can revert the change by doing this:
cd /usr/src
fetch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Here is a patch that adjusts parameters of the interrupt handler, which
reduces interrupts. These parameters are obtained from DragonFly, FYI.
Note that this does not restore previous behavior, say, few interrupt if
no traffic. I'm still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi guys,
I think I got a real fix.
Cheers,
- --
Xin LI [EMAIL PROTECTED] http://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)
22 matches
Mail list logo
