From: Sujit K M <sjt.kar@gmail.com>
To: mell@hedrich-winders.com, linux-rt-users@vger.kernel.org
Subject: Re: Problem with function select on kernel 2.6.29.6-rt23
Date: Thu, 10 Sep 2009 17:03:19 +0530 [thread overview]
Message-ID: <921ca19c0909100433s2cad9e6asc6b3a77a7e03aa1a@mail.gmail.com> (raw)
In-Reply-To: <4AA8D958.5000508@hedrich-winders.com>
Could you Check the sort of load that your server machine is able to
take. The site you would be looking at is
http://www.petefreitag.com/item/689.cfm.
I think if the network is rejecting the select call, As the socket is
not getting created. Other wise it would wait to the required 2 Second
limit set by you.
Also are you sure of the bind part of the socket creation. Making it
threaded is an option.
Thanks,
Sujit
On Thu, Sep 10, 2009 at 4:17 PM, Jürgen Mell <mell@hedrich-winders.com> wrote:
> Hi,
>
> I have an application which connects via a network socket to a server
> running on the same machine (IP 127.0.0.1) This application uses the
> function 'select' to wait for new data from the server or until a two
> seconds timeout. This works well until there is network traffic on the
> external network interfaces (eth* or WLAN). When there is network traffic on
> the external interfaces, the select function does not wait anymore but it
> returns with a return code of zero, indicating not data available on the
> socket. This happens nearly immediately (after 8 to 9 microseconds) and not
> after the specified two seconds interval. The timeout parameter of select is
> updated accordingly (it shows eg. 1 s 999991 us).
> Up to now I could not test this with another kernel but I will try to do it
> this afternoon. Are there any known problems with select? Is there any way
> to circumvent this?
>
> Any help would be greatly appreciated!
>
> Jürgen
>
> --
> Jürgen Mell (Software-Entwicklung) mell@hedrich-winders.com
> Tel.: +49-511-762-18226 http://www.hedrich-winding.com
> FAX : +49-511-762-18225
> Mobil: +49-160-7428156
> ----------------------------------------------------------------------------
> HEDRICH winding systems GmbH
> An der Universität 2 (im PZH)
> D-30823 Garbsen (GERMANY)
> ----------------------------------------------------------------------------
> Geschäftsführer: Karsten Adam
> Handelsregister: Wetzlar, HRB 4768
> Steuernr.: 020/235/20110 USt-IdNr.: DE 258258279
> ----------------------------------------------------------------------------
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
-- Sujit K M
blog(http://kmsujit.blogspot.com/)
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-09-10 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 10:47 Problem with function select on kernel 2.6.29.6-rt23 Jürgen Mell
2009-09-10 11:33 ` Sujit K M [this message]
2009-09-10 11:50 ` Jürgen Mell
2009-09-18 19:40 ` Jürgen Mell
2009-09-20 10:20 ` Sujit K M
2009-09-21 9:23 ` Sujit K M
2009-09-21 9:58 ` Jürgen Mell
2009-09-21 10:34 ` Jürgen Mell
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=921ca19c0909100433s2cad9e6asc6b3a77a7e03aa1a@mail.gmail.com \
--to=sjt.kar@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=mell@hedrich-winders.com \
/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