From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.38
Date: Mon, 22 Jan 2007 18:59:47 +0300 [thread overview]
Message-ID: <200701221859.47380.a1426z@gawab.com> (raw)
H. Peter Anvin wrote:
> Ralf Baechle wrote:
> > On Sun, Jan 21, 2007 at 06:37:24PM +0200, S.ط£â€،aط¤إ¸lar Onur wrote:
> >> 21 Oca 2007 Paz tarihinde ط¥إ¸unlarط¤ï؟½ yazmط¤ï؟½ط¥إ¸tط¤ï؟½nط¤ï؟½z:
> >>> RSS feed of the git tree:
> >>> http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.gi
> >>>t;a=r
> >>
> >> I already mailed to webmaster _at_ kernel.org 2 days ago but still all
> >> RSS feeds gaves "Internal Server Error"
> >
> > kernel.org is not in quite the best shape currently due to the machines'
> > massive overload, so this may take a little while to get fixed.
>
> Do note that www2.kernel.org has a load that is usually 1/20th of
> www1.kernel.org; apparently due to Microsoft DNS braindamage (which
> affects anyone whose ISP uses MS-DNS.) Using www2.kernel.org explicitly
> is likely to give you better performance. HOWEVER, performance is going
> to suck due to the measures we've had to take on the servers regardless,
> and it's entirely likely git-rss is totally broken. Again, we should
> have a dedicated git server in operation in about a month.
It's rather sad to see kernel.org ppl resort to ms tactics to fix sw problems
by throwing more hardware into the mess.
My hunch, it's a scheduler problem. Try spa_no-frills with xfs.
Thanks!
--
Al
next reply other threads:[~2007-01-22 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 15:59 Al Boldi [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-21 16:09 Adrian Bunk
2007-01-21 16:37 ` S.Çağlar Onur
2007-01-21 19:02 ` Ralf Baechle
2007-01-21 20:58 ` H. Peter Anvin
2007-01-21 20:48 ` H. Peter Anvin
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=200701221859.47380.a1426z@gawab.com \
--to=a1426z@gawab.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
Powered by JetHome