netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zacco <zacco@fw.hu>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: David Miller <davem@davemloft.net>,
	baruch@ev-en.org, netdev@vger.kernel.org
Subject: Re: many sockets, slow sendto
Date: Sun, 22 Apr 2007 14:34:18 +0200	[thread overview]
Message-ID: <462B564A.2020109@fw.hu> (raw)
In-Reply-To: <20070330151021.d067d837.dada1@cosmosbay.com>

Hi Eric and all,

Thanks a lot. However, some chunks still resisted to apply, the manual
patching worked. I tested and the results are more than satisfactory.
Not just the reception part became faster, but also the bind calls. The
gain is especially significant when increasing the hash table size. I
applied it in an older kernel with similar success. Basically, my
problem is solved.

I have just one question: Why do you check the address in
__udp_lib_port_inuse? I think it is enough to check the port, as the
name of the function suggests, but I may be wrong. I removed it and the
patch still works fine, but for me this is not a proof, as I may use it
in some special case.

As for your confusion: You're right. My idea to include the both sockets
in the hash function was really unnecessary, even in my example. Thx for
revealing that!

I applied another modification in the patch: I called the hash function
from __udp_lib_port_inuse, instead passing the hash value. This way, I
could reduce the number modifications, so the patch is easier to apply
manually to whatever kernel version.

Thx: Zacco


Eric Dumazet wrote:
> On Thu, 29 Mar 2007 21:24:31 +0200
> Zacco <zacco@fw.hu> wrote:
>
>   
>> Hi,
>>
>> Thanks for the patch. I almost dare not confess that I don't know which 
>> version to apply to. I tried 3 different ones (2.6.19-r5-gentoo, 
>> 2.6.20.1 and 2.6.21-rc4), but in the best case at least two hunks 
>> failed. Nevertheless, I applied the patches manually. In each case, UDP 
>> stopped working. I guess, you checked the patch and worked. I don't 
>> think I made a mistake in the manual copy, and it seems unlikely that 
>> your patch interfered with other parallel changes in the kernel - but, 
>> I'm just guessing ...
>> I think, I'd better send you the spec and code, as you suggested that 
>> first we have a common understanding of the issue. I must have failed in 
>> passing the point. I'm removing irrelevant stuff, and I send it to you 
>> as soon as I can (sorry for my long delays).
>>
>> thx a lot,
>> Zacco
>>     
>
> Hum, please find a (working) patch against linux-2.6.21-rc5
>
> (first patch was against net-2.6.22 git tree and had one bug)
>
> ...

  reply	other threads:[~2007-04-22 12:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 15:08 many sockets, slow sendto Zaccomer Lajos
2007-03-06 18:20 ` Baruch Even
2007-03-19 23:10   ` Zacco
2007-03-19 23:16     ` David Miller
2007-03-20 21:59       ` Zacco
2007-03-20 22:48         ` Eric Dumazet
2007-03-21 21:53           ` Zacco
2007-03-21 22:24             ` Eric Dumazet
2007-03-21 23:26             ` Eric Dumazet
2007-03-22  1:14             ` David Miller
2007-03-21 22:12           ` Eric Dumazet
2007-03-22  1:15             ` David Miller
2007-03-22  6:43               ` Eric Dumazet
2007-03-29 19:24             ` Zacco
2007-03-30 13:10               ` Eric Dumazet
2007-04-22 12:34                 ` Zacco [this message]
2007-04-30  7:26             ` David Miller
2007-04-30 10:56               ` YOSHIFUJI Hideaki / 吉藤英明
2007-04-30 12:47                 ` Eric Dumazet
2007-04-30 19:43                   ` YOSHIFUJI Hideaki / 吉藤英明
2007-04-30 19:59                     ` Eric Dumazet
2007-03-06 19:23 ` Andi Kleen
2007-03-06 21:28   ` Zacco

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=462B564A.2020109@fw.hu \
    --to=zacco@fw.hu \
    --cc=baruch@ev-en.org \
    --cc=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --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).