All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Jerone Young <jyoung5@us.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Net grant tables breaking multiple nic domU
Date: Tue, 13 Sep 2005 14:04:48 -0700	[thread overview]
Message-ID: <43273EF0.2080004@us.ibm.com> (raw)
In-Reply-To: <1126644880.3029.2.camel@thinkpad>

Jerone Young wrote:

>>Did you not see Jim Dykman's updates and posts on this bug?
>>He's found the root cause, and is putting together a patch,
>>although some of it might be interim because it exposes
>>another resource shortage which will have to be addressed
>>somehow. Expect a patch from him in the next day or two,
>>and see the bugzilla entry (and previous posts on xen-devel)
>>from Jim for the details.
> 
> 
> Yes I did see this. But if that is the case then why does disabling net
> grant tables fix the problem? So I just decided to come to the list to
> see if someone understanding the net grant table code might know.

The cause he identified is in the net grant code, so
there is no conflict here, is there?  When you disable
the net grant code, it doesn't use net grant tables,
but falls back to the earlier code, which doesn't have
the bug. Yes, we could disable the net grant stuff, but
as we discussed in previous threads on this list, that
is a temporary workaround, and since this is the code
we want to ship in 3.0, I see the correct thing to do is
to find and fix the real problem, which Jim is doing.

thanks,
Nivedita

  reply	other threads:[~2005-09-13 21:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 20:33 Net grant tables breaking multiple nic domU Jerone Young
2005-09-13 20:50 ` Nivedita Singhvi
2005-09-13 20:54   ` Jerone Young
2005-09-13 21:04     ` Nivedita Singhvi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-14 12:03 Ian Pratt

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=43273EF0.2080004@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=jyoung5@us.ibm.com \
    --cc=xen-devel@lists.xensource.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 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.