netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Moni Shoua <monis@voltaire.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
	jeff@garzik.org, David Miller <davem@davemloft.net>,
	ogerlitz@voltaire.com, netdev@vger.kernel.org
Subject: Re: [PATCH] IB/ipoib: Bound the net device to the ipoib_neigh structue
Date: Wed, 10 Oct 2007 11:31:30 -0700	[thread overview]
Message-ID: <aday7eaddod.fsf@cisco.com> (raw)
In-Reply-To: <470CF7E1.6060503@voltaire.com> (Moni Shoua's message of "Wed, 10 Oct 2007 18:03:45 +0200")

 > I also ran a test for the code in the branch of 2.6.24 and found a problem.
 > I see that ifconfig down doesn't return (for IPoIB interfaces) and it's stuck in napi_disable() in the kernel (any idea why?)

For what it's worth, I took the upstream 2.6.23 git tree and merged in
Dave's latest net-2.6.24 tree and my latest for-2.6.24 tree and tried
that.  I brought up an IPoIB interface, sent a few pings, and did
ifconfig down, and it worked fine.

Can you try the same thing without the bonding patches to see if your
setup works OK too?

Also can you give more details about what you do to get ifconfig down stuck?

 - R.

  reply	other threads:[~2007-10-10 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11916151232222-git-send-email-fubar@us.ibm.com>
     [not found] ` <470C200D.4010705@pobox.com>
2007-10-10  0:56   ` [PATCH] IB/ipoib: Bound the net device to the ipoib_neigh structue Jeff Garzik
2007-10-10  1:12     ` David Miller
2007-10-10  1:18       ` Jay Vosburgh
2007-10-10 16:03         ` Moni Shoua
2007-10-10 18:31           ` Roland Dreier [this message]
2007-10-11 14:48             ` Moni Shoua
2007-10-11 20:17               ` Roland Dreier
2007-10-11 22:01                 ` Jay Vosburgh
2007-10-13 15:24                 ` Moni Shoua
2007-10-14 15:51                 ` Moni Shoua

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=aday7eaddod.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=davem@davemloft.net \
    --cc=fubar@us.ibm.com \
    --cc=jeff@garzik.org \
    --cc=monis@voltaire.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@voltaire.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;
as well as URLs for NNTP newsgroup(s).