From: Xavier Bestel <xavier.bestel@free.fr>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Morten Welinder <mwelinder@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Deleting large files
Date: Wed, 07 May 2008 22:17:36 +0200 [thread overview]
Message-ID: <1210191456.14754.1.camel@bip.parateam.prv> (raw)
In-Reply-To: <alpine.LNX.1.10.0805072208140.30395@fbirervta.pbzchgretzou.qr>
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
next prev parent reply other threads:[~2008-05-07 20:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 19:49 Morten Welinder
2008-05-07 20:10 ` Jan Engelhardt
2008-05-07 20:17 ` Xavier Bestel [this message]
2008-05-07 20:48 ` Jan Engelhardt
2008-05-07 22:34 ` linux-os (Dick Johnson)
2008-05-07 23:14 ` Morten Welinder
2008-05-08 23:01 ` Alan Cox
2008-05-11 10:30 ` Jan Engelhardt
2008-05-11 16:38 ` Enrico Weigelt
2008-05-20 14:33 ` Pavel Machek
2008-05-08 8:19 ` Matti Aarnio
2008-05-11 11:16 ` Christoph Hellwig
2008-05-11 16:42 ` Aneesh Kumar K.V
2008-05-08 17:29 ` Christian Kujau
[not found] ` <118833cc0805081110u7aad3921v3a1ec4187acc4ef4@mail.gmail.com>
2008-05-08 18:54 ` Christian Kujau
2008-05-17 12:15 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1210191456.14754.1.camel@bip.parateam.prv \
--to=xavier.bestel@free.fr \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mwelinder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®