linux-kernel - Re: Deleting large files

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1210191456.14754.1.camel@bip.parateam.prv>
Date:	Wed, 07 May 2008 22:17:36 +0200
From:	Xavier Bestel <xavier.bestel@...e.fr>
To:	Jan Engelhardt <jengelh@...ozas.de>
Cc:	Morten Welinder <mwelinder@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Deleting large files

Le mercredi 07 mai 2008 à 22:10 +0200, Jan Engelhardt a écrit :
> 
> >I.e., could unlink do the directory changes and then hand off the rest of the
> >task to a kernel thread?
> 
> Say you had one realtime application running that would do lots of new
> writes after the unlink finished. When the unlink is put into the
> background, you interleave the unlink operation with new writes,
> probably causing needless seeks and therefore not hitting the deadlines
> anymore.

Why ? The writes are delayed, so could be the unlink operations.

	Xav


--
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/