mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "tj@kernel.org" <tj@kernel.org>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"cl@linux.com" <cl@linux.com>
Subject: Re: [PATCH 3/4]percpu_counter: fix code for 32bit systems
Date: Wed, 13 Apr 2011 12:50:37 +0900	[thread overview]
Message-ID: <20110413035037.GA24161@mtj.dyndns.org> (raw)
In-Reply-To: <1302663781.3981.169.camel@sli10-conroe>

Hello, guys.

On Wed, Apr 13, 2011 at 11:03:01AM +0800, Shaohua Li wrote:
> I can do this, but please give a reason. If network code is the only
> place requiring disable irq, why not network code do it?

This thread is pointless.  The next patch converts it to atomic64_t
and the lock is removed anyway.  I think Eric's argument makes sense
given that atomic64_t translates into irqsave spinlock (it has to) in
generic 32bit implementation.  That said, this is all a moot point.
We might as well simply drop this patch and directly convert to
atomic64_t.

Thanks.

-- 
tejun

  reply	other threads:[~2011-04-13  3:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12  8:04 Shaohua Li
2011-04-12  9:03 ` Eric Dumazet
2011-04-13  1:01   ` Shaohua Li
2011-04-13  2:32     ` Eric Dumazet
2011-04-13  2:41       ` Shaohua Li
2011-04-13  2:47         ` Eric Dumazet
2011-04-13  3:03           ` Shaohua Li
2011-04-13  3:50             ` tj [this message]
2011-04-13  4:37               ` Shaohua Li
2011-04-13  3:53             ` Eric Dumazet
2011-04-13  4:00               ` tj
2011-04-12 19:02 ` Tejun Heo
2011-04-13  1:05   ` Shaohua Li

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=20110413035037.GA24161@mtj.dyndns.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.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®