linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: 2.4.x high irq contention
@ 2003-04-22 18:44 Chuck Ebbert
  0 siblings, 0 replies; 6+ messages in thread
From: Chuck Ebbert @ 2003-04-22 18:44 UTC (permalink / raw)
  To: linux-kernel


>> Won't help a lot. If its all IRQ load (eg lots of multicast streaming
>> audio small frames) then you want an eepro100 or something similar that
>> has interrupt mitigators.
>
> Well, handwaving about the network load/type ;-)
> Could as well be two RTL back-to-back, normal packets but high bandwidth. 
> (watch collisions for this case :-)


  RTL-8139: the hardware equivalent of a bicycle.

  8))
------
 Chuck

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.4.x high irq contention
  2003-04-22 13:47   ` Alan Cox
@ 2003-04-22 17:50     ` Stephan von Krawczynski
  0 siblings, 0 replies; 6+ messages in thread
From: Stephan von Krawczynski @ 2003-04-22 17:50 UTC (permalink / raw)
  To: Alan Cox; +Cc: casus, linux-kernel

On 22 Apr 2003 14:47:53 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Maw, 2003-04-22 at 11:40, Stephan von Krawczynski wrote:
> > 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.
> 
> Won't help a lot. If its all IRQ load (eg lots of multicast streaming
> audio small frames) then you want an eepro100 or something similar that
> has interrupt mitigators.

Well, handwaving about the network load/type ;-)
Could as well be two RTL back-to-back, normal packets but high bandwidth. 
(watch collisions for this case :-)

Regards,
Stephan


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.4.x high irq contention
  2003-04-22 10:40 ` Stephan von Krawczynski
@ 2003-04-22 13:47   ` Alan Cox
  2003-04-22 17:50     ` Stephan von Krawczynski
  0 siblings, 1 reply; 6+ messages in thread
From: Alan Cox @ 2003-04-22 13:47 UTC (permalink / raw)
  To: Stephan von Krawczynski; +Cc: Anton Petrusevich, Linux Kernel Mailing List

On Maw, 2003-04-22 at 11:40, Stephan von Krawczynski wrote:
> 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.

Won't help a lot. If its all IRQ load (eg lots of multicast streaming
audio small frames) then you want an eepro100 or something similar that
has interrupt mitigators.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.4.x high irq contention
  2003-04-22  3:32 Anton Petrusevich
@ 2003-04-22 10:40 ` Stephan von Krawczynski
  2003-04-22 13:47   ` Alan Cox
  0 siblings, 1 reply; 6+ messages in thread
From: Stephan von Krawczynski @ 2003-04-22 10:40 UTC (permalink / raw)
  To: Anton Petrusevich; +Cc: linux-kernel

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/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* 2.4.x high irq contention
@ 2003-04-22 10:12 Chuck Ebbert
  0 siblings, 0 replies; 6+ messages in thread
From: Chuck Ebbert @ 2003-04-22 10:12 UTC (permalink / raw)
  To: Anton Petrusevich; +Cc: linux-kernel


> 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.


  Get a real network card. ;)

  I found two used Compaq NC-3121 (Intel e100) for $15 each...



------
 Chuck

^ permalink raw reply	[flat|nested] 6+ messages in thread

* 2.4.x high irq contention
@ 2003-04-22  3:32 Anton Petrusevich
  2003-04-22 10:40 ` Stephan von Krawczynski
  0 siblings, 1 reply; 6+ messages in thread
From: Anton Petrusevich @ 2003-04-22  3:32 UTC (permalink / raw)
  To: linux-kernel

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


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2003-04-22 18:36 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-22 18:44 2.4.x high irq contention Chuck Ebbert
  -- strict thread matches above, loose matches on Subject: below --
2003-04-22 10:12 Chuck Ebbert
2003-04-22  3:32 Anton Petrusevich
2003-04-22 10:40 ` Stephan von Krawczynski
2003-04-22 13:47   ` Alan Cox
2003-04-22 17:50     ` Stephan von Krawczynski

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).