From: Oleg Nesterov <oleg@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ming Lei <tom.leiming@gmail.com>, Shaohua Li <shli@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: + atomic-improve-atomic_inc_unless_negative-atomic_dec_unless_positive .patch added to -mm tree
Date: Fri, 22 Mar 2013 13:59:00 +0100 [thread overview]
Message-ID: <20130322125900.GA12647@redhat.com> (raw)
In-Reply-To: <1363906618.4431.37.camel@edumazet-glaptop>
On 03/21, Eric Dumazet wrote:
>
> On Thu, 2013-03-21 at 19:30 +0100, Oleg Nesterov wrote:
>
> > To me, it would be better to kill atomic_inc_not_zero_hint() or unify
> > unify it with atomic_inc_not_zero(). But this is another story.
>
> git is your friend.
>
> I suggest you read 3f9d35b9514 changelog before killing it, thanks.
Thanks Eric for your friendly suggestion.
But I didn't mean we should kill this optimization. Yes, I am wondering
if we can avoid inc_not_zero_hint _or_ unify with add_unless. But let me
repeat, this is another story.
Perhaps I misread your previous email... I understood it as if you think
the patch I sent is wrong. No?
If you meant that get_write_access() can predict the current value of
i_writecount... how? And even if we could, why we cant/shouldnt try to
optimize the generic atomic_inc_unless_negative()?
So what did you actually mean?
Oleg.
next prev parent reply other threads:[~2013-03-22 13:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 16:24 + atomic-improve-atomic_inc_unless_negative-atomic_dec_unless_positive .patch added to -mm tree Oleg Nesterov
2013-03-15 3:46 ` Ming Lei
2013-03-15 13:46 ` Oleg Nesterov
2013-03-15 15:13 ` Ming Lei
2013-03-15 16:51 ` Oleg Nesterov
2013-03-15 17:23 ` Frederic Weisbecker
2013-03-15 17:51 ` Oleg Nesterov
2013-03-15 18:34 ` Frederic Weisbecker
2013-03-15 20:17 ` Paul E. McKenney
2013-03-16 18:30 ` Oleg Nesterov
2013-03-17 17:26 ` Paul E. McKenney
2013-03-21 17:08 ` Oleg Nesterov
2013-03-21 17:34 ` Paul E. McKenney
2013-03-21 18:03 ` Eric Dumazet
2013-03-21 18:30 ` Oleg Nesterov
2013-03-21 22:56 ` Eric Dumazet
2013-03-22 12:59 ` Oleg Nesterov [this message]
2013-03-22 16:34 ` Paul E. McKenney
2013-03-16 18:19 ` Oleg Nesterov
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=20130322125900.GA12647@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=shli@kernel.org \
--cc=tom.leiming@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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.