All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gordan Bobic <lartc@bobich.net>
To: lartc@vger.kernel.org
Subject: [LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Traffic)
Date: Sat, 22 Mar 2003 13:16:09 +0000	[thread overview]
Message-ID: <marc-lartc-104833907511635@msgid-missing> (raw)

On Thursday 20 March 2003 23:36, Julian Anastasov wrote:
> Hello,
>
> On Thu, 20 Mar 2003, Gordan Bobic wrote:
> > Provided the DS9 patch works for me, is it possible to somehow prioritize
> > what is dropped first and what is dropped last? Something like attaching
> > a prio/cbq to the ingress qdisc? For example, I want SSH/POP3/IMAP4
> > traffic to be dropped last, and FTP/SMTP traffic to be dropped first. Can
> > ingress support in DS9 do this, or is it limited to indiscriminately
> > dropping traffic?
>
> 	Except if someone has another idea, may be only dropping.
> I'm not sure there is IMQ for 2.2 :)

It doesn't appear to be there with the patches I applied... :-(

> May be you can look at
> Edge31-ca-u32 from the iproute2 examples, there are some ideas
> about using policers.

I have tried the ingress policing when the new patches, but according to my 
mrtg graphs, it still doesn't seem to work, even in it's simplest form. I 
THINK I saw it work with FTP, though (connection throttled), so I am not 
sure. It could be that it works initially, then stops later. I will 
investigate further...

> As for DS9, it tries to provide the same
> interface to all qos objects as in 2.4, so it is possible to do
> the same things as in 2.4, of course, there is one problem, nobody
> wants to support new features in 2.2 :)

Yeah, I know. I will upgrade at some point. ;-)

I seem to be having a problem with the newly applied patches, though. After 
6-8 hours, I get a kernel crash. Black screen od death, hex dumps, Aiee, 
killing interrupt handler, trying to kill idle task, etc. This happened 
twice, so it seems unlikely to be a coincidence, as the only patches applied 
were the DS9, rtree, HTB3 and routes. It used to be stable before. I am 
hoping that it is ingress related stuff that kills it, so I have turned that 
off (everything to do with ingress). We'll see if I get another crash now. If 
not, than it would appear that it is ingress policing that kills it after a 
while.

I will report back on this when I know more.

Regards.

Gordan
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-03-22 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-22 13:16 Gordan Bobic [this message]
2003-03-23 13:49 ` [LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Julian Anastasov
2003-03-23 17:51 ` [LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Traffic) Gordan Bobic
2003-03-24 22:32 ` Gordan Bobic

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=marc-lartc-104833907511635@msgid-missing \
    --to=lartc@bobich.net \
    --cc=lartc@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 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.