From: mukesh.fkd@gmail.com (Mukesh Yadav)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Packet drop while using BPF filter
Date: Wed, 21 Dec 2011 00:08:04 +0530 [thread overview]
Message-ID: <CACPS-PuMisxusXKsTVB8LxDKGbzjjTatQrp4RoED2a7sLzsZQg@mail.gmail.com> (raw)
Hi Guys,
I am working on user level code which uses BPF filter.
Solution has two threads and BPF filter for incoming packets to raw socket
dedicated to each thread.
Intent is to divide ingress traffic between two thread based on whether
dest IP is even or odd.
BPF filters used are:
Even IP filter :-> tcpdump -i interface 'ether dst <dest mac> && ip[19] &
0x01 = 0'
Odd IP filter :-> tcpdump -i interface 'ether dst <dest mac> && ip[19] &
0x01 = 1'
There is a packet loss for odd IP thread even when CPU is available. Reason
being packet drop due recv buffer full.
Same amount of traffic is well handled by even IP thread(user code being
same in both), scaling CPU to full 100%.
In odd IP thread, If filter is changed to "tcpdump -i interface 'ether dst
<dest mac> && ip proto 17' ", all goes fine.
Also CPU usage at kernel drops from 50% to 4 % for a particular amount of
traffic.
Would appreciate any I/ps for reducing load at kernel for packet
filtering(Odd/Even IP distribution)
Cheers
Mukesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20111221/129e99c3/attachment.html
next reply other threads:[~2011-12-20 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 18:38 Mukesh Yadav [this message]
2011-12-21 0:52 ` Packet drop while using BPF filter Mulyadi Santosa
2011-12-21 5:25 ` Mukesh Yadav
2011-12-21 16:59 ` Mulyadi Santosa
2011-12-22 13:48 ` Raghavendra D Prabhu
2011-12-24 16:27 ` Mukesh Yadav
2011-12-24 18:54 ` Raghavendra D Prabhu
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=CACPS-PuMisxusXKsTVB8LxDKGbzjjTatQrp4RoED2a7sLzsZQg@mail.gmail.com \
--to=mukesh.fkd@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).