Re: Improving read/write/close system call reliability when used with pthreads

> POSIX appears to leave it "implementation-defined" provided I  
> interpret this correctly, of course. So wouldn't it be great to make  
> one of the current results a reliable feature?

Given that 99.99% of programs don't appear to care and you materially
slow down a critical path for every read and write I'm skeptical. 

Teaching the pipe code specifically to behave more nicely in this case
might be worthwhile (and as it happens with sockets in the same case you
can use shutdown() before close to get your preferred behaviour)

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Improving read/write/close system call reliability when used with pthreads
    • From: Fredrik Noring <[email protected]>

• References:
  • Improving read/write/close system call reliability when used with pthreads
    • From: Fredrik Noring <[email protected]>
  • Re: Improving read/write/close system call reliability when used with pthreads
    • From: Alan Cox <[email protected]>
  • Re: Improving read/write/close system call reliability when used with pthreads
    • From: Fredrik Noring <[email protected]>

• Prev by Date: Re: ACPI: thermal: create "thermal.off=1" to disable ACPI thermal support
• Next by Date: troubles with r8169
• Previous by thread: Re: Improving read/write/close system call reliability when used with pthreads
• Next by thread: Re: Improving read/write/close system call reliability when used with pthreads
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]