[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: conversion to zmpoll - scheduler busyloops
- To: "Eugene Crosser" <crosser@rol.ru>
- Subject: Re: conversion to zmpoll - scheduler busyloops
- From: "Dawid Kuroczko" <qnex42@gmail.com>
- Date: Fri, 27 Oct 2006 15:00:11 +0200
- Cc: zmailer@nic.funet.fi, koc@rol.ru
- DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=N73ZFuuOPhtIf1K3WzAFqHwzBkK9maWaBxm9LeXRoxXuRA0UCKKn7jpTgmWeifrTjr2b1UZV2Jnz/VBMEV5bAQ7//fcRE0xWZdWZYHHTaa1rxe8ihxpKATjCAHGX5pYU77BS2cAigC94fxPY07j5JkydE6MlZG9Rtj3LTm9v0e8=
- In-Reply-To: <4540DBFB.5020104@rol.ru>
- Original-Recipient: rfc822;zmailer-log@nic.funet.fi
- References: <4540DBFB.5020104@rol.ru>
- Sender: zmailer-owner@nic.funet.fi
On 10/26/06, Eugene Crosser <crosser@rol.ru> wrote:
> We (I now have a colleague who assists me in mail system maintenance)
> noticed that after recent changes scheduler busyloops on poll().
> Investigation of the source revealed that the loop on cpids[] terminates
> on condition "i < maxf", where maxf is max file descriptor rather than
> max used cpids[] slot.
Right. That was a thinko on my part...
[...]
> I also noticed that maxf and highfd are (almost) redundant, aren't they?
The original select(2) code had a maxf variable, and the router zmpoll
code (on which I was basing mine) had a highfd variable. While I was
modifying the code I left most of the "old" code intact, so I could
gradually move from select(2) to zmpoll(). And then I commented
out most unneeded code; this one I must have missed.
Regards,
Dawid
-
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi