From: Eric Dumazet <eric.dumazet@gmail.com>
To: Sam Roberts <vieuxtech@gmail.com>
Cc: Kuzin Andrey <kuzinandrey@yandex.ru>,
Anders Nilsson Plymoth <lanilsson@gmail.com>,
netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: netfilter queue throughput slowdown
Date: Fri, 01 Jul 2011 06:52:06 +0200 [thread overview]
Message-ID: <1309495926.2515.8.camel@edumazet-laptop> (raw)
In-Reply-To: <BANLkTiksYHMU7ojnKMJBj-EQjW8sxTO2Tw@mail.gmail.com>
Le jeudi 30 juin 2011 à 15:26 -0700, Sam Roberts a écrit :
> On Wed, Jun 29, 2011 at 11:20 PM, Kuzin Andrey <kuzinandrey@yandex.ru> wrote:
> > On 29.06.2011 14:08, Eric Dumazet wrote:
> >> But if some packets are never dequeued (because something is wrong with
> >> your program, failing to give verdict), they stay forever in the list
> >> and each dequeue is slower since it has to go past these packets...
>
> > I'am using NFQUEUE several years on our main network router, and problem
> > with packets stuck in the queue is still not resolved.
>
> Is there any way to see what the current queue is in the kernel? How
> deep, and what the IDs are?
>
check third column (queue_total) of :
# cat /proc/net/netfilter/nfnetlink_queue
0 15363 1024 2 65535 160 0 2208 1
queue_number peer_pid queue_total copy_mode copy_range queue_dropped queue_user_dropped id_sequence 1
Here my test program 'forgot' to give a verdict to 1024 packets.
So all new packets are dropped (160 so far)
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-01 4:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 9:17 netfilter queue throughput slowdown Anders Nilsson Plymoth
2011-06-29 9:47 ` Eric Dumazet
2011-06-29 9:55 ` Anders Nilsson Plymoth
2011-06-29 10:08 ` Eric Dumazet
2011-06-30 6:20 ` Kuzin Andrey
2011-06-30 6:47 ` Eric Dumazet
2011-06-30 7:36 ` Kuzin Andrey
2011-06-30 11:34 ` Eric Dumazet
2011-06-30 11:59 ` Patrick McHardy
2011-06-30 15:15 ` Eric Dumazet
2011-06-30 14:32 ` Stephen Clark
2011-06-30 14:51 ` Patrick McHardy
2011-06-30 17:07 ` Eric Leblond
2011-06-30 17:45 ` Eric Dumazet
2011-06-30 18:08 ` Eric Leblond
2011-07-01 6:39 ` Amos Jeffries
2011-07-01 7:00 ` [RFC] nfnetlink_queue not scalable Eric Dumazet
2011-07-01 7:49 ` Florian Westphal
2011-07-01 15:27 ` [PATCH 1/2] nfnetlink: add RCU in nfnetlink_rcv_msg() Eric Dumazet
2011-07-01 14:11 ` Florian Westphal
2011-07-05 13:22 ` Patrick McHardy
2011-07-18 14:06 ` Patrick McHardy
2011-07-01 15:08 ` netfilter queue throughput slowdown Anders Nilsson Plymoth
2011-06-30 22:24 ` Sam Roberts
2011-07-01 4:53 ` Eric Dumazet
2011-06-30 22:26 ` Sam Roberts
2011-07-01 4:52 ` Eric Dumazet [this message]
2011-07-02 12:25 ` Pablo Neira Ayuso
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=1309495926.2515.8.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=kuzinandrey@yandex.ru \
--cc=lanilsson@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=vieuxtech@gmail.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.