All of lore.kernel.org
 help / color / mirror / Atom feed
From: "evilninja@gmx.net" <evilninja@gmx.net>
To: reiserfs-list@namesys.com
Cc: Francesco Biscani <biscani@pd.astro.it>
Subject: Re: More Slowdown
Date: Thu, 17 Nov 2005 01:46:41 +0100	[thread overview]
Message-ID: <437BD2F1.2030509@gmx.net> (raw)
In-Reply-To: <200511160240.45212.biscani@pd.astro.it>

Francesco Biscani schrieb:
> What are the implications of doing something like this? Is "sync" going to 
> stop working or isn't it using this function?

sync(8) won't stop working, because it's using sync(2):

% strace -T sync 2>&1 | grep sync
execve("/bin/sync", ["sync"], [/* 20 vars */]) = 0
sync()                                  = 0 <0.213305>


...but can someone explain to me: what's the difference between sync(2) 
and fsync(2) ? why are there 2 systemcalls, why is fsync(2) expensive 
and (mis?)used so often by applications and sync(2) is cheap (not?) and 
used only by sync(8)? the manpages say:

fsync, fdatasync -
	synchronize a file's complete in-core state with that on disk

sync -
	commit buffer cache to disk

but both syscalls do not guarantee  data  integrity anyway, because 
"modern disks have large caches".

thank you,
Christian.
-- 
BOFH excuse #453:

Spider infestation in warm case parts

  parent reply	other threads:[~2005-11-17  0:46 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 22:22 More Slowdown Thorsten Hirsch
2005-11-15 22:55 ` Artur Makówka
2005-11-15 23:09   ` Andreas Rosander
2005-11-15 23:13     ` Avuton Olrich
2005-11-15 23:23       ` Artur Makówka
2005-11-15 23:44       ` Craig Shelley
2005-11-16  0:45         ` David Masover
2005-11-16  1:40           ` Francesco Biscani
2005-11-16 12:18             ` Nikita Danilov
2005-11-16 13:28               ` John Gilmore
2005-11-16 17:28               ` David Masover
2005-11-17  0:46             ` evilninja [this message]
2005-11-16 18:18   ` Artur Makówka
  -- strict thread matches above, loose matches on Subject: below --
2005-11-17 13:47 Hesse, Christian
2005-11-22 10:23 ` Marcel Hilzinger
2005-11-22 10:38   ` Sander
2005-11-22 10:44     ` Marcel Hilzinger
2005-11-22 14:29       ` David Masover
2005-11-22 15:01         ` Marcel Hilzinger
2005-11-22 19:15           ` David Masover
2005-11-22 23:17         ` Hans Reiser
2005-11-22 15:08       ` Sander
2005-11-22 11:34   ` Ingo Bormuth
2005-11-22 12:29     ` Artur Makówka
2005-11-11 13:59 Slowdown is gone & apt-get works with updated reiser4. So nevermind John Gilmore
2005-11-12  3:07 ` michael chang
2005-11-12  6:38   ` Hans Reiser
2005-11-12  9:06     ` John Gilmore
2005-11-14 19:41       ` More Slowdown Craig Shelley
2005-11-14 19:53         ` jp
2005-11-14 20:47         ` Christian Iversen
2005-11-15 14:27           ` Craig Shelley
2005-11-15 18:04             ` Laurent Riffard
2005-11-15 18:42               ` Craig Shelley
     [not found]                 ` <437AF653.9040001@namesys.com>
2005-11-16  9:33                   ` Craig Shelley
2005-11-17  3:08             ` michael chang
2005-11-17  4:49               ` Hans Reiser
2005-11-17 12:02                 ` Artur Makówka
2005-11-17 12:40                   ` Vladimir V. Saveliev
2005-11-17 10:34                     ` John Gilmore
2005-11-17 21:12                       ` Hans Reiser
2005-11-18 20:45                   ` Hans Reiser
2005-11-17  8:56               ` Ingo Bormuth
2005-11-17  9:36               ` PFC
2005-11-17 21:08                 ` Hans Reiser
2005-11-19  4:44                   ` michael chang

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=437BD2F1.2030509@gmx.net \
    --to=evilninja@gmx.net \
    --cc=biscani@pd.astro.it \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.