Linux-kernel mailing list archive 2000-15,: Re: O_CLOEXEC

# Re: O_CLOEXEC

Richard Gooch (rgooch@ras.ucalgary.ca)
Wed, 12 Apr 2000 08:35:53 -0600

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Ed Carp: "Re: EXT2 and BadBlock updating....."
- Previous message: Jan Niehusmann: "Re: EXT2 and BadBlock updating....."
- In reply to: Alan Cox: "Re: O_CLOEXEC"

Alan Cox writes:
> > which automatically sets the FD_CLOEXEC flag for the new file
> > descriptor. I've never heard a reason why this wasn't implemented.
> > It could save quite a few system calls in various daemons and also the
> > libc.
>
> How many of them on critical performance paths. How many times would
> the flag be tested and not acted on. Every condition costs

If we do decide to add this flag, how about building a mask of common
and uncommon flags, and put all the uncommon tests behind a single
test? That way we can keep the fast path lean, yet still add flags if
required.

Regards,

Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: Ed Carp: "Re: EXT2 and BadBlock updating....."
- Previous message: Jan Niehusmann: "Re: EXT2 and BadBlock updating....."
- In reply to: Alan Cox: "Re: O_CLOEXEC"