netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: John Miller <forall@mail15.com>, netdev@vger.kernel.org
Subject: Re: UDP packet loss when running lsof
Date: Tue, 22 May 2007 08:47:40 +0200	[thread overview]
Message-ID: <4652920C.8020608@cosmosbay.com> (raw)
In-Reply-To: <46528973.50809@cosmosbay.com>

Eric Dumazet a écrit :
> John Miller a écrit :
>> Hi Eric,
>>
>>> I CCed netdev since this stuff is about network and not
>>> lkml.
>>
>> Ok, dropped the CC...
>>
>>> What kind of machine do you have ? SMP or not ?
>>
>> It's a HP system with two dual core CPUs at 3GHz, the
>> storage system is connected through QLogic FC-HBA. It should
>> really be fast enough to handle a data stream of 50 MB/s...
> 
> Then you might try to bind network IRQ to one CPU
> (echo 1 >/proc/irq/XX/smp_affinity)
> 
> XX being your NIC interrupt (cat /proc/interrupts to catch it)
> 
> and bind your user program to another cpu(s)
> 
> You might hit a cond_resched_softirq() bug that Ingo and others are 
> sorting out right now. Using separate CPU for softirq handling and your 
> programs should help a lot here.

You might try this patch, now that Ingo "Signed-off-by" it.

http://marc.info/?l=linux-kernel&m=117981607429875&w=2


I guess that with a correct softirq resched, no need to play with IRQ 
affinities, unless you really want to push performance.


  reply	other threads:[~2007-05-22  6:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <loom.20070521T090409-252@post.gmane.org>
     [not found] ` <20070521113503.6bb70ae4.dada1@cosmosbay.com>
2007-05-21 22:12   ` UDP packet loss when running lsof John Miller
2007-05-22  6:10     ` Eric Dumazet
2007-05-22  6:47       ` Eric Dumazet [this message]
2007-05-22 22:42       ` John Miller

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=4652920C.8020608@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=forall@mail15.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).