public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: Dan Kegel <dank@kegel.com>
Cc: x@xman.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Niels Provos <provos@citi.umich.edu>,
	Charles Lever <Charles.Lever@netapp.com>
Subject: Re: Improving (network) IO performance ...
Date: Thu, 12 Jul 2001 08:34:53 -0700 (PDT)	[thread overview]
Message-ID: <XFMail.20010712083453.davidel@xmailserver.org> (raw)
In-Reply-To: <3B4DBFDC.91C27FFB@kegel.com>


On 12-Jul-2001 Dan Kegel wrote:
> Yes, in fact, it shows that adding more dead connections actually
> improves performance using your patch :-)
> 
> Here's what the little birdie told me exactly:
>> You'll be happy to know I've achieved over 500,000 connections
>> on Pentium hardware with 4G of RAM and 2 1Gbit cards on FreeBSD 4.3.
> 
> I think the application was similar to your benchmark configuration;
> no idea what the ratio of live to dead connections was.
> Let's see: if you have 1/32nd as much RAM as she had, you ought to 
> be able to handle 1/32nd as many connections, right?  Since you
> hit 16000 connections, I guess you just about did.

I've done a couple of changes to the patch :

1) moved the file callback list handling from fs/file.c to fs/fcblist.c

2) moved the functions definitions from include/linux/file.h to
        include/linux/fcblist.h

3) added a new kernel config param CONFIG_FCBLIST

4) renamed the patch from /dev/poll to /dev/epoll ( event poll )

5) renamed the devpoll.c(.h) files into eventpoll.c(.h)

6) made CONFIG_EPOLL dependent of CONFIG_FCBLIST

7) fixed a locking issue on SMP

8) kmalloc/vmalloc switch for big chunks of mem

9) increased the maximum number of fds to 128000 ( maybe I'll change this to be
        unbounded )


The new stuff will be published today in the same link :

http://www.xmailserver.org/linux-patches/nio-improve.html

About the old /dev/poll patch it seems to have problems when the number of
connections go over 8000-9000.
I don't know what it could be coz I've looked deeply inside the patch.
Maybe Niels or Charles can be more precise about this issue.




- Davide


  reply	other threads:[~2001-07-12 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12  0:39 Improving (network) IO performance Dan Kegel
2001-07-12  5:08 ` Davide Libenzi
2001-07-12 15:18   ` Dan Kegel
2001-07-12 15:34     ` Davide Libenzi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-11 21:59 Davide Libenzi

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=XFMail.20010712083453.davidel@xmailserver.org \
    --to=davidel@xmailserver.org \
    --cc=Charles.Lever@netapp.com \
    --cc=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=provos@citi.umich.edu \
    --cc=x@xman.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