From: Davy Durham <pubaddr2@davyandbeth.com>
To: bert hubert <bert.hubert@netherlabs.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: select() efficiency / epoll
Date: Tue, 23 Aug 2005 06:01:15 -0500 [thread overview]
Message-ID: <430B01FB.2070903@davyandbeth.com> (raw)
In-Reply-To: <20050823182405.GA21301@outpost.ds9a.nl>
bert hubert wrote:
>On Tue, Aug 23, 2005 at 04:49:14AM -0500, Davy Durham wrote:
>
>
>
>>However, I'm getting segfaults because some pointers in places are
>>getting set to low integer values (which didn't used to have those values).
>>
>>
>
>epoll is pretty heavily benchmarked and hence tested. I don't entirely
>understand the remark above and suggest looking at the generated core dumps.
>
>
>
I just mean that when I debug and catch the segv, it's dies because
some pointers now have corrupted values. (usually because something is
overwriting some memory some where)
I'm currently re-writing some code to make it use select() instead of
epoll_wait() and see if everything is suddently fixed. If so, then I
will suspect that epoll has a problem. But it's still not ruled out
being my fault since it could be a timing issue that makes the crash
show up.
next prev parent reply other threads:[~2005-08-23 18:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 21:18 select() efficiency Davy Durham
2005-07-22 21:24 ` bert hubert
2005-08-23 9:49 ` select() efficiency / epoll Davy Durham
2005-08-23 18:24 ` bert hubert
2005-08-23 11:01 ` Davy Durham [this message]
2005-08-23 11:25 ` Davy Durham
2005-08-23 19:12 ` Willy Tarreau
2005-08-23 11:24 ` Davy Durham
2005-08-23 19:45 ` Willy Tarreau
2005-08-23 11:55 ` Davy Durham
2005-08-23 20:20 ` Willy Tarreau
2005-08-23 23:21 ` Davide Libenzi
2005-08-23 17:08 ` Davy Durham
2005-08-24 5:09 ` Davide Libenzi
2005-08-23 22:35 ` Davy Durham
2005-08-23 19:30 ` Jari Sundell
2005-08-23 11:53 ` Davy Durham
2005-08-23 20:42 ` Jari Sundell
2005-08-23 17:11 ` Davy Durham
2005-08-23 17:40 ` Davy Durham
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=430B01FB.2070903@davyandbeth.com \
--to=pubaddr2@davyandbeth.com \
--cc=bert.hubert@netherlabs.nl \
--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.