From: Jarek Poplawski <jarkao2@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
cfriesen@nortel.com, davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: questions on NAPI processing latency and dropped network packets
Date: Wed, 16 Jan 2008 23:42:44 +0100 [thread overview]
Message-ID: <20080116224244.GA2626@ami.dom.local> (raw)
In-Reply-To: <20080116200458.GC8953@1wt.eu>
On Wed, Jan 16, 2008 at 09:04:58PM +0100, Willy Tarreau wrote:
...
> you can work with latest release provided that you always have a fallback
> to an earlier one. That way, you don't bet too much on something you don't
> completely control. If it works, it tells you you'll be able to completely
> exploit its new possibilities in next product release, and if it breaks,
> it's easy to issue a fix to get back to earlier, well-tested version.
Of course, this way looks preferable, but sometimes maybe too costly,
especially with some complex systems. Actually, I don't even think
this have to be fully (production ready) implemented or workable.
Probably there would be even enough to maintain some simplified kind
of test checking how current kernel changes could affect such a system,
and how new versions of this system are better, BTW.
Regards,
Jarek P.
next prev parent reply other threads:[~2008-01-16 22:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 17:24 questions on NAPI processing latency and dropped network packets Chris Friesen
2008-01-10 17:37 ` Kok, Auke
2008-01-10 18:12 ` Chris Friesen
2008-01-10 18:26 ` Kok, Auke
2008-01-10 18:25 ` James Chapman
2008-01-10 21:29 ` Chris Friesen
2008-01-10 18:41 ` Rick Jones
2008-01-10 19:01 ` Kok, Auke
2008-01-11 1:20 ` David Miller
2008-01-11 14:59 ` Chris Friesen
2008-01-11 22:29 ` Herbert Xu
2008-01-12 1:53 ` David Miller
2008-01-14 15:58 ` Chris Friesen
2008-01-15 7:19 ` Jarek Poplawski
2008-01-15 14:47 ` Chris Friesen
2008-01-15 15:17 ` Radoslaw Szkodzinski
2008-01-15 17:14 ` Chris Friesen
2008-01-15 17:23 ` Eric Dumazet
2008-01-15 20:29 ` Jarek Poplawski
2008-01-16 0:17 ` Herbert Xu
2008-01-16 6:58 ` Jarek Poplawski
2008-01-16 20:04 ` Willy Tarreau
2008-01-16 22:42 ` Jarek Poplawski [this message]
2008-01-12 5:37 ` Ray Lee
2008-01-14 15:49 ` Chris Friesen
2008-01-14 16:56 ` Eric Dumazet
2008-01-14 19:25 ` Chris Friesen
2008-01-14 19:33 ` Eric Dumazet
2008-01-14 20:02 ` Chris Friesen
2008-01-15 15:09 ` Vlad Yasevich
2008-01-21 19:53 ` Chris Friesen
2008-01-21 21:11 ` Ben Greear
2008-01-21 23:15 ` Chris Friesen
2008-01-21 23:32 ` Ben Greear
2008-01-21 21:31 ` Eric Dumazet
2008-01-21 23:25 ` Chris Friesen
2008-01-22 5:46 ` Eric Dumazet
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=20080116224244.GA2626@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=cfriesen@nortel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=w@1wt.eu \
/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).