From: Dave Jones <davej@redhat.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: imcdnzl@gmail.com, greearb@candelatech.com,
herbert@gondor.apana.org.au, netdev@vger.kernel.org,
stable@kernel.org, fedora-list@list.zikzak.de,
fedoralist@kotoulas.de
Subject: Re: latest -stable breaks Squid
Date: Thu, 4 May 2006 19:47:42 -0400 [thread overview]
Message-ID: <20060504234742.GS18962@redhat.com> (raw)
In-Reply-To: <20060504.162546.88959729.davem@davemloft.net>
On Thu, May 04, 2006 at 04:25:46PM -0700, David S. Miller wrote:
> That being said, the first thing that should be tried is reverting
> the above mentioned change and see if the problem goes away. If
> so, then we need to investigate what the bandwidth delay product is
> for the connection, and whether the socket send buffer is set large
> enough for that size of pipe.
It's now believed (after some detective work from Herbert) that
this round of problems wasn't caused by the -stable patch, but
by a bogus update to Xen which we carry in the Fedora kernel
that sneaked in without a changelog (which is why I didn't even suspect that thing
given it worked fine previously).
Until today I had no idea just how much that thing poked into net/
Ugh. Apologies for the false alarm.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-05-04 23:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 21:19 latest -stable breaks Squid Dave Jones
2006-05-04 0:43 ` Dave Jones
2006-05-04 1:10 ` Herbert Xu
2006-05-04 1:22 ` Ben Greear
2006-05-04 1:59 ` Ian McDonald
2006-05-04 23:25 ` David S. Miller
2006-05-04 23:30 ` Herbert Xu
2006-05-04 23:47 ` Dave Jones [this message]
2006-05-05 8:49 ` [x86_64, NET] smp_rmb() in dst_destroy() seems very expensive, ditto in kfree_skb() Eric Dumazet
2006-05-05 10:06 ` Herbert Xu
2006-05-05 16:13 ` Very long list of struct dst_entry in dst_garbage_list Eric Dumazet
2006-05-05 17:05 ` [x86_64, NET] smp_rmb() in dst_destroy() seems very expensive, ditto in kfree_skb() Andi Kleen
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=20060504234742.GS18962@redhat.com \
--to=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=fedora-list@list.zikzak.de \
--cc=fedoralist@kotoulas.de \
--cc=greearb@candelatech.com \
--cc=herbert@gondor.apana.org.au \
--cc=imcdnzl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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 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.