mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Daniel McNeil <daniel@osdl.org>
Cc: andrea@suse.de, linux-kernel@vger.kernel.org,
	shemminger@osdl.org, torvalds@transmeta.com
Subject: Re: [PATCH 2.5.64 2/2] i_size atomic access
Date: Fri, 7 Mar 2003 16:30:01 -0800	[thread overview]
Message-ID: <20030307163001.43805e11.akpm@digeo.com> (raw)
In-Reply-To: <1047082543.2636.98.camel@ibm-c.pdx.osdl.net>

Daniel McNeil <daniel@osdl.org> wrote:
>
> This adds i_seqcnt to inode structure and then uses i_size_read() and
> i_size_write() to provide atomic access to i_size.

Ho hum.  Everybody absolutely hates this, but I guess we should do it :(

> +static inline void i_size_write(struct inode * inode, loff_t i_size)
> +{
> +#if BITS_PER_LONG==32 && defined(CONFIG_SMP)
> +	write_seqcntbegin(&inode->i_size_seqcnt);
> +	inode->i_size = i_size;
> +	write_seqcntend(&inode->i_size_seqcnt);
> +#elif BITS_PER_LONG==32 && defined(CONFIG_PREMPT)
> +	prempt_disable();
> +	inode->i_size = i_size;
> +	prempt_enable();
> +#else
> +	inode->i_size = i_size;
> +#endif
> +}

You've used "PREMPT" and "prempt" throughput the patch.  It is in fact
"PREEMPT" and "preempt".

Could you please fix that up and send me fresh copies?  Probably as
attachments - your mailer wordwrapped the patches.

Thanks.

  reply	other threads:[~2003-03-08  0:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-08  0:15 Daniel McNeil
2003-03-08  0:30 ` Andrew Morton [this message]
2003-03-08  1:26   ` Daniel McNeil
     [not found]     ` <20030308042555.GA31650@delft.aura.cs.cmu.edu>
     [not found]       ` <20030307203340.5e025ef0.akpm@digeo.com>
2003-03-10 13:16         ` Andrea Arcangeli
2003-03-10 17:22           ` Daniel McNeil

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=20030307163001.43805e11.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=andrea@suse.de \
    --cc=daniel@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@osdl.org \
    --cc=torvalds@transmeta.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®