Skip to content

tee: should we use fadvise (POSIX_FADV_SEQUENTIAL) for file input? #12654

@oech3

Description

@oech3

We don't have

$ strace -qqq -e trace='/fadvise' gnu9.11/tee
fadvise64(0, 0, 0, POSIX_FADV_SEQUENTIAL) = 0
$ echo 1|strace -qqq -e trace='/fadvise' gnu9.11/tee
fadvise64(0, 0, 0, POSIX_FADV_SEQUENTIAL) = -1 ESPIPE (Illegal seek)

It is easy to do same thing as we already do for tsort, etc... but in my thought, the most common usecase for tee is multicasting stream input instead of multicasting <file.

Should we pay that cost for non-major usecase?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions