From: Stephen Hemminger <shemminger@vyatta.com>
To: ratheesh k <ratheesh.ksz@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: rx interrupt in userspace
Date: Tue, 20 Apr 2010 11:00:03 -0700 [thread overview]
Message-ID: <20100420110003.29685143@nehalam> (raw)
In-Reply-To: <p2mcfeab66d1004201031u233ce827w8874c7ecf45575f6@mail.gmail.com>
On Tue, 20 Apr 2010 23:01:38 +0530
ratheesh k <ratheesh.ksz@gmail.com> wrote:
> Hi ,
>
> When flooding of network packets happens on network card , my
> linux embedded box becomes unrepsonsive because softirq_rx eats up
> hell a lot of CPU . I want top half of tx interrupt to be in User
> space . I want to implement some alogoritm in userspace to drop
> packets on high flooding and to keep other processes's some cycles .
>
> Could you guide me a little on this , any online turorials or articles
> or books , i can refer ?
> Any similar implementation like this ?
>
If your driver used NAPI, then it would not do this.
prev parent reply other threads:[~2010-04-20 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 17:31 rx interrupt in userspace ratheesh k
2010-04-20 18:00 ` Stephen Hemminger [this message]
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=20100420110003.29685143@nehalam \
--to=shemminger@vyatta.com \
--cc=netfilter@vger.kernel.org \
--cc=ratheesh.ksz@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 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).