From: khandelw@cs.fsu.edu
To: jyotiraditya@softhome.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Select/Poll
Date: Wed, 2 Jun 2004 11:28:29 -0400 [thread overview]
Message-ID: <1086190109.a0ea5ca71914e@system.cs.fsu.edu> (raw)
In-Reply-To: <courier.40BD66BD.00006D7D@softhome.net>
Hello,
Can you give more details - Like which machine which vendor etc.,
On a sony vaio pcg frv31 laptop/ redhat 9.0/ after firing some 36,000+ request
my select multiplexed server used to fail. With select I believe you not get
any packet loss...
- Amit
PS. If you can post the code that will be great...
Quoting jyotiraditya@softhome.net:
> Hello All,
>
> In one of the threads named: "Linux's implementation of poll() not
> scalable?'
> Linus has stated the following:
> **************
> Neither poll() nor select() have this problem: they don't get more
> expensive as you have more and more events - their expense is the number
> of file descriptors, not the number of events per se. In fact, both poll()
> and select() tend to perform _better_ when you have pending events, as
> they are both amenable to optimizations when there is no need for waiting,
> and scanning the arrays can use early-out semantics.
> **************
>
> Please help me understand the above.. I'm using select in a server to read
> on multiple FDs and the clients are dumping messages (of fixed size) in a
> loop on these FDs and the server maintainig those FDs is not able to get all
> the messages.. Some of the last messages sent by each client are lost.
> If the number of clients and hence the number of FDs (in the server) is
> increased the loss of data is proportional.
> eg: 5 clients send messages (100 each) to 1 server and server receives
> 96 messages from each client.
> 10 clients send messages (100 by each) to 1 server and server again
> receives 96 from each client.
>
> If a small sleep in introduced between sending messages the loss of data
> decreases.
> Also please explain the algorithm select uses to read messages on FDs and
> how does it perform better when number of FDs increases.
>
> Thanks and Regards,
> Jyotiraditya
> -
> 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:[~2004-06-02 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 5:33 Select/Poll jyotiraditya
2004-06-02 5:54 ` Select/Poll David Schwartz
2004-06-02 6:12 ` Select/Poll Ben Greear
2004-06-02 6:38 ` Select/Poll bert hubert
2004-06-02 6:09 ` Select/Poll Ben Greear
2004-06-02 7:05 ` Select/Poll Vadim Lobanov
2004-06-02 14:11 ` Select/Poll Davide Libenzi
2004-06-02 15:28 ` khandelw [this message]
2004-06-03 15:10 ` Select/Poll Mike Jagdis
2004-06-03 15:53 ` Select/Poll khandelw
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=1086190109.a0ea5ca71914e@system.cs.fsu.edu \
--to=khandelw@cs.fsu.edu \
--cc=jyotiraditya@softhome.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.