From: Stephan von Krawczynski <skraw@ithnet.com>
To: Anton Petrusevich <casus@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x high irq contention
Date: Tue, 22 Apr 2003 12:40:42 +0200 [thread overview]
Message-ID: <20030422124042.200a3a60.skraw@ithnet.com> (raw)
In-Reply-To: <20030422033201.GA523@casus.home.my>
I don't know much about your network load, but if you have a lot, then you
should probably throw away the 8139 network card and use tulip or 3com instead.
Regards,
Stephan
On Tue, 22 Apr 2003 10:32:01 +0700
Anton Petrusevich <casus@mail.ru> wrote:
> Hi people,
>
> This is 2.4.21-pre4aa3, but the same applies to 2.4.20-vanilla, and i
> think to any 2.4.x. The NIC is RTL-8139(8139too). I would really like to
> know what could be done in this situation. The machine (p3-1GHz) is almost
> unrespobsible. Yes, there are really network card interrupts. So, here it
> goes.
> # readprofile -m /boot/System.map | sort -nr +2 | head -20
> 2600 handle_IRQ_event 23.2143
> 268 system_call 4.7857
> 184 fget 3.8333
> 123 sock_poll 2.5625
> 421 kfree 2.1927
> 101 __free_pages 2.1042
> 288 do_softirq 2.0000
> 326 skb_copy_and_csum_dev 1.8523
> 56 restore_fpu 1.7500
> 232 send_sig_info 1.6111
> 123 poll_freewait 1.5375
> 174 __wake_up 1.3594
> 695 do_schedule 1.2776
> 19 sockfs_delete_dentry 1.1875
> 70 del_timer 1.0938
> 592 save_i387 1.0278
> 17 ret_from_sys_call 1.0000
> 111 skb_release_data 0.9911
> 58 __generic_copy_to_user 0.9062
> 115 do_pollfd 0.8984
>
> --
> Anton Petrusevich
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-04-22 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 3:32 Anton Petrusevich
2003-04-22 10:40 ` Stephan von Krawczynski [this message]
2003-04-22 13:47 ` Alan Cox
2003-04-22 17:50 ` Stephan von Krawczynski
2003-04-22 10:12 Chuck Ebbert
2003-04-22 18:44 Chuck Ebbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030422124042.200a3a60.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=casus@mail.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®