Sponsored Content
Full Discussion: Which is more expensive ?
Top Forums Programming Which is more expensive ? Post 302131746 by vino on Monday 13th of August 2007 01:55:39 PM
Old 08-13-2007
Quote:
Originally Posted by reborg
I don't think there would be any real difference here, there might me a very marginal improvement in the second case due to the number of comparison you are doing, but would expect that to be marginal. You are after all incrementing the same number of times in both cases anc calling close() the same number of time.

Just curious, is this shutdown code or is it after forking that you are closing the open fds?
This is for closing the open fds after forking. I was told that you generally need to close only 64 fds instead of the RLIMIT.rlim_cur after forking. Any thoughts ?
 

2 More Discussions You Might Find Interesting

1. Programming

calling pthread_self (on ubuntu), expensive?

Hi all, Is anyone aware of what operations are involved when a call to pthread_self() is made, obtaining the unique thread ID on a Ubuntu system (or even any Linux flavour)? Specifically, to retrieve the thread id, is there any locking required or atomic operations? I'm building an... (11 Replies)
Discussion started by: gorga
11 Replies

2. What is on Your Mind?

Very Expensive Running Shoes

You really should not need one third of the entire US budget to buy a pair of running shoes... even if they are name brand. What have these guys been smoking? It reminds me of the old joke... Customer: At those prices you aren't going to sell many shoes. Salesman: Ah, but all we need to do is... (4 Replies)
Discussion started by: Perderabo
4 Replies
explain_poll_or_die(3)					     Library Functions Manual					    explain_poll_or_die(3)

NAME
explain_poll_or_die - wait for some event on file descriptor and report errors SYNOPSIS
#include <libexplain/poll.h> int explain_poll_or_die(struct pollfd *fds, int nfds, int timeout); int explain_poll_on_error(struct pollfd *fds, int nfds, int timeout); DESCRIPTION
The explain_poll_or_die function is used to call the poll(2) system call. On failure an explanation will be printed to stderr, obtained from the explain_poll(3) function, and then the process terminates by calling exit(EXIT_FAILURE). The explain_poll_on_error function is used to call the poll(2) system call. On failure an explanation will be printed to stderr, obtained from the explain_poll(3) function, but still returns to the caller. fds The fds, exactly as to be passed to the poll(2) system call. nfds The nfds, exactly as to be passed to the poll(2) system call. timeout The timeout, exactly as to be passed to the poll(2) system call. RETURN VALUE
The explain_poll_or_die function only returns on success, see poll(2) for more information. On failure, prints an explanation and exits, it does not return. The explain_poll_on_error function always returns the value return by the wrapped poll(2) system call. EXAMPLE
The explain_poll_or_die function is intended to be used in a fashion similar to the following example: int result = explain_poll_or_die(fds, nfds, timeout); SEE ALSO
poll(2) wait for some event on a file descriptor explain_poll(3) explain poll(2) errors exit(2) terminate the calling process COPYRIGHT
libexplain version 0.52 Copyright (C) 2010 Peter Miller explain_poll_or_die(3)
All times are GMT -4. The time now is 09:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy