Re: xfs_file_splice_read: possible circular locking dependency detected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Sep 13, 2016 at 8:16 PM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote:
>
>> So feel free to try maxing out using only a small handful of
>> pipe_buffer entries. Returning partial IO from splice() is fine.
>
>         Are you sure that nobody's growing the output pipe buffer before
> doing splice() into it as a way to reduce the amount of iterations?

Do we care?

There's a lot of people who use large buffers. That doesn't
necessarily mean that it is the right thing to do. A small buffer that
we can allocate on-stack might well be better even if it causes more
iterations.

I'd also like to simplify the splice code if at all possible.
Particularly as there really aren't necessarily all that many actual
users of it. So if we can say "screw that" and just allocate a small
buffer on stack, and people end up iterating a bit more, so what? The
point of splice is to avoid the data copies and VM games, not to make
big buffers.

             Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux