[TUHS] v3 pipes

25 Apr 2020

...
   why the single
fd approach was abandoned? To its credit, it appears to allow for limited 2-way
communication.  My understanding is that the single file descriptor broke the
open-file
 model, which had a single read/write pointer. Two-way communication via 
I’m not sure I understand.

In the implementation, the read pointer is file location offset (“fp->f_offset”) and
the write pointer is the file size (“ip->i_size”). The location offset on the writing
end of the pipe is always zero, and on the reading end it moves between zero and PIPSIZ
(but that is unobservable).

I just tried making both pipe ends readable+writeable in my “V6.5” kernel and that appears
to work. It allows for bi-directional communication in a half-duplex sense (i.e
communicating walky-talky style). The other benefit is using just one file descriptor, at
a time when a process had just 15 to work with.

Maybe the issue was that two sides writing to a full pipe at the same time will cause
deadlock?

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

[TUHS] v3 pipes