Linux SNPS ARC Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: anthony.yznaga@oracle.com (Anthony Yznaga)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH 2/3] fs: inode_set_flags() replace opencoded set_mask_bits()
Date: Thu, 10 Jan 2019 20:24:43 -0800	[thread overview]
Message-ID: <5c9bf6bd-e29b-c985-b686-35f6dc272152@oracle.com> (raw)
In-Reply-To: <1547166387-19785-3-git-send-email-vgupta@synopsys.com>



On 1/10/19 4:26 PM, Vineet Gupta wrote:
> It seems that 5f16f3225b0624 and 00a1a053ebe5, both with same commitlog
> ("ext4: atomically set inode->i_flags in ext4_set_inode_flags()")
> introduced the set_mask_bits API, but somehow missed not using it in
> ext4 in the end
>
> Also, set_mask_bits is used in fs quite a bit and we can possibly come up
> with a generic llsc based implementation (w/o the cmpxchg loop)
>
> Cc: Alexander Viro <viro at zeniv.linux.org.uk>
> Cc: Theodore Ts'o <tytso at mit.edu>
> Cc: Peter Zijlstra (Intel) <peterz at infradead.org>
> Cc: linux-fsdevel at vger.kernel.org
> Cc: linux-kernel at vger.kernel.org
> Signed-off-by: Vineet Gupta <vgupta at synopsys.com>
>

Reviewed-by: Anthony Yznaga <anthony.yznaga at oracle.com>

  reply	other threads:[~2019-01-11  4:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11  0:26 [PATCH 0/3] Replace opencoded set_mask_bits Vineet Gupta
2019-01-11  0:26 ` [PATCH 1/3] coredump: Replace opencoded set_mask_bits() Vineet Gupta
2019-01-11  4:24   ` Anthony Yznaga
2019-01-11  0:26 ` [PATCH 2/3] fs: inode_set_flags() replace " Vineet Gupta
2019-01-11  4:24   ` Anthony Yznaga [this message]
2019-01-11  0:26 ` [PATCH 3/3] bitops.h: set_mask_bits() to return old value Vineet Gupta
2019-01-11  4:25   ` Anthony Yznaga
2019-01-11  9:24   ` Peter Zijlstra
2019-01-11 20:58     ` Vineet Gupta
2019-01-14 19:00   ` Will Deacon

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=5c9bf6bd-e29b-c985-b686-35f6dc272152@oracle.com \
    --to=anthony.yznaga@oracle.com \
    --cc=linux-snps-arc@lists.infradead.org \
    /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