From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: lock_kernel() usage and sync_*() functions
Date: Thu, 22 Mar 2001 15:45:44 +0100 [thread overview]
Message-ID: <20010322154544.B11126@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <99bsbk$a6n$1@penguin.transmeta.com> <Pine.GSO.4.21.0103212354420.2632-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0103212354420.2632-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Thu, Mar 22, 2001 at 12:18:27AM -0500
On Thu, Mar 22, 2001 at 12:18:27AM -0500, Alexander Viro wrote:
>
> I started with adding
> void invalidate_dev(kdev_t dev, int sync_flag)
> {
> struct super_block *sb = get_super(dev);
> if (sync_flag == 1)
> sync_dev(dev);
> else if (sync_flag == 2)
> fsync_dev(dev);
> if (sb) {
> invalidate_inodes(sb);
> /* drop_super(sb); here */
> }
> invalidate_buffers(dev);
> }
Could we remove the "magic" sync_flag from the exported interface?
Do sth. like renaming your invalidate_dev() to
_invalidate_dev() and adding 3 defines:
#define invalidate_dev(dev) _invalidate_dev(dev,0)
#define invalidate_dev_sync(dev) _invalidate_dev(dev,1)
#define invalidate_dev_fsync(dev) _invalidate_dev(dev,2)
This would make it quite clear, what will be done.
AFAIR Linus dosn't like these magic numers either, right?
Regards
Ingo Oeser
--
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< been there and had much fun >>>>>>>>>>>>
next prev parent reply other threads:[~2001-03-22 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 3:11 Nigel Gamble
2001-03-22 3:42 ` Linus Torvalds
2001-03-22 5:18 ` Alexander Viro
2001-03-22 14:45 ` Ingo Oeser [this message]
2001-03-22 17:20 ` Alexander Viro
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=20010322154544.B11126@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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®