Question

I’m looking for the best way to read data from an stdin pipe in C programming.

Problem : I need to seek on this data, ie I need to read data from the start of the stream after reading some data at the end of this same stream.

Small use case : gunzip -c 4GbDataFile.gz | myprogram

Another one :

1. On local host : nc -l -p 1234 | myprogram
2. On remote host : gunzip -c 4GbDataFile.gz | nc -q 0 theotherhost 1234

I know that reading from fifo can be done only once. So, at the moment :

• I slurp everything from stdin to memory and work from this allocated memory.

It’s ugly, but it works. An evident issue is that if someone sends a huge (or a continuous) stream to my app, I’ll end with a big allocated memory chunk or I’ll run out of memory. (Think about an 8Gb file)

What I thought next :

• I set a size limit (maybe user-defined) of that memory chunk. Once I’ve read this much data from stdin :
  1. Either I stop here : “Errr. Out of memory, bazinga. Forget it.” style.
  2. Either I start dumping what I am reading to a file and work from this file once all data is read.

But then, what is the point? I can not find out the origin of the data that I am reading. If this is a local 8Gb file, I’ll be dumping it to another 8Gb file on the same system.

So, my question is :

How do you read efficiently a lot of data from an stdinpipe when you have to seek back and forth in it?

Thanks in advance for your answers.

Edit :

My program needs to read metadata somewhere (depending of the file format) in the given file, so that maybe at the end of the stream. Then it may read back other data at the start of the stream, then at another place etc. In short : it needs to have access to any bytes of the data.

An example would be to read data of an archive file without knowing the file format before starting to read from stdin: I need to check the archive metadata, find archive files names and offsets etc.

So I’ll make a local copy of stdin content and work from it. Thanks everyone for your inputs 😉

Answer 1

The data structure in your 4GbDataFile just doesn’t lend itself to what you want to do. Think outside the box. Don’t hammer your program into something it shouldn’t even attempt. Try to fix the input format where it is generated so you don’t need to seek back 4 GB.

In case you do like hammering: 4GB of in-core memory is pretty expensive. Instead, save the data read from stdin in a file, then open the file (or mmap it) and seek to your heart’s content.