public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Keiichi KII <k-keiichi@bx.jp.nec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 2.6.19 2/6] support multiple logging agents
Date: Wed, 20 Dec 2006 10:40:46 -0600	[thread overview]
Message-ID: <20061220164046.GW13687@waste.org> (raw)
In-Reply-To: <458903ED.9040207@bx.jp.nec.com>

On Wed, Dec 20, 2006 at 06:35:41PM +0900, Keiichi KII wrote:
> >>  static struct netpoll np = {
> >> >      .name = "netconsole",
> >> >      .dev_name = "eth0",
> >> > @@ -69,23 +84,91 @@ static struct netpoll np = {
> >> >      .drop = netpoll_queue,
> >> >  };
> >
> > Shouldn't this piece get dropped in this patch?
> >
> 
> This piece isn't in -mm tree, but this piece is in 2.6.19.
> Which version should I follow ?

-mm, probably.

> >> -static int configured = 0;
> >> +static int add_netcon_dev(const char* target_opt)
> >> +{
> >> +    static atomic_t netcon_dev_count = ATOMIC_INIT(0);
> >
> > Hiding this inside a function seems wrong. Why do we need a count? If
> > we've already got a spinlock, why does it need to be atomic?
> >
> 
> We don't have a spinlock for add_netcon_dev, because we don't need
> to get a spinlock for add_netcon_dev except for list operation.
> So, it must be atomic.

Or you can just increment the list counter inside the lock.

> 
> >>      local_irq_save(flags);
> >> +    spin_lock(&netconsole_dev_list_lock);
> >>      for(left = len; left; ) {
> >>          frag = min(left, MAX_PRINT_CHUNK);
> >> -        netpoll_send_udp(&np, msg, frag);
> >> +        list_for_each_entry(dev, &active_netconsole_dev, list) {
> >> +            spin_lock(&dev->netpoll_lock);
> >> +            netpoll_send_udp(&dev->np, msg, frag);
> >> +            spin_unlock(&dev->netpoll_lock);
> >
> > Why do we need a lock here? Why isn't the list lock sufficient? What
> > happens if either lock is held when we get here?
> >
> 
> The netpoll_lock is for each structure containing information related to 
> netpoll
> (remote IP address and port, local IP address and port and so on).
> If we don't take a spinlock for each structure, the target IP address and 
> port
> number are subject to change on the way sending packets.

Why can't you simply define the list lock as protecting all the
structures on the list?

-- 
Mathematics is the supreme nostalgia of our time.

      reply	other threads:[~2006-12-20 17:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12  6:17 [RFC][PATCH 2.6.19 0/6] proposal for dynamic configurable netconsole Keiichi KII
2006-12-12  6:28 ` [RFC][PATCH 2.6.19 1/6] cleanup for netconsole Keiichi KII
2006-12-12 18:10   ` Matt Mackall
2006-12-12  6:34 ` [RFC][PATCH 2.6.19 3/6] add interface for netconsole using sysfs Keiichi KII
2006-12-12 19:09   ` Matt Mackall
2006-12-12  6:36 ` [RFC][PATCH 2.6.19 4/6] switch function of netpoll Keiichi KII
2006-12-12 19:15   ` Matt Mackall
2006-12-12  6:37 ` [RFC][PATCH 2.6.19 5/6] add "add" element in /sys/class/misc/netconsole Keiichi KII
2006-12-12 19:27   ` Matt Mackall
2006-12-12  6:38 ` [RFC][PATCH 2.6.19 6/6] update modification history Keiichi KII
2006-12-13 23:50   ` Stephen Hemminger
2006-12-12 18:13 ` [RFC][PATCH 2.6.19 0/6] proposal for dynamic configurable netconsole Matt Mackall
2006-12-13  9:44   ` Keiichi KII
     [not found] ` <457E4C65.6030802@bx.jp.nec.com>
2006-12-12 18:42   ` [RFC][PATCH 2.6.19 2/6] support multiple logging agents Matt Mackall
2006-12-13 21:16     ` Andy Isaacson
2006-12-20  9:35     ` Keiichi KII
2006-12-20 16:40       ` Matt Mackall [this message]

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=20061220164046.GW13687@waste.org \
    --to=mpm@selenic.com \
    --cc=k-keiichi@bx.jp.nec.com \
    --cc=linux-kernel@vger.kernel.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