linux-kernel - sendfile/splice - Non-blocking input?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 30 May 2011 10:45:59 +0200
From:	Aiko Barz <aiko@...oot.de>
To:	linux-kernel@...r.kernel.org
Subject: sendfile/splice - Non-blocking input?

Hello,

is sendfile/splice completely non-blocking on the input side?

I am writing a small webserver for educational reasons. I use epoll to
deal with the network part. From what I have read, I have to avoid
blocking code under all circumstances. And the linux implementation
of sendfile seems to block until the file enters the pagecache.

Most of the docs are not completely up to date. I figured out, that
sendfile is now a frontend for splice. So, does it still block?

Or differently asked: May I call sendfile directly from the few epoll
threads or do I have to execute sendfile/splice within independent
worker threads?

Kind regards,
	Aiko Barz
-- 
:wq ✉
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/