All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Claude Robitaille <clauder@accedian.com>
Cc: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>,
	netdev@vger.kernel.org
Subject: Re: sk_buff handling in packet handler
Date: Sun, 17 May 2009 22:38:47 -0700	[thread overview]
Message-ID: <20090517223847.168d9ebd@nehalam> (raw)
In-Reply-To: <4A104825.4000201@accedian.com>

On Sun, 17 May 2009 13:23:49 -0400
Claude Robitaille <clauder@accedian.com> wrote:

> Thanks Mark.
> 
> very interesting
> 
> this helped me but just to get to next problem....
> 
> what I am trying to do is to receive frame using a packet handler, 
> manipulate it and send a portion of it over a UDP channel. I am using 
> sock_sendmsg. Things sort of work but I get some warnings while in 
> net_tx_action (via the sendmsg I am guessing) about doing scheduling 
> while in atomic and sometime the kernel simply completely crashes. All 
> this probably means that using kernel socket functions cannot be used 
> from any context.... Any suggestion on how to properly do this? 
> Ultimately, I'd like to avoid copying the data so if I could simply send 
> an skb to some UDP TX handler would be ideal but if not, what is the 
> best approach?
> 

Write a netfilter module, it is easier to do what you are trying to
do with iptables rules.

> 


-- 

  reply	other threads:[~2009-05-18  5:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-17  0:55 sk_buff handling in packet handler Mark Smith
2009-05-17 17:23 ` Claude Robitaille
2009-05-18  5:38   ` Stephen Hemminger [this message]
2009-05-19 22:41 ` Claude Robitaille
  -- strict thread matches above, loose matches on Subject: below --
2009-05-16 16:31 Claude Robitaille
2009-05-16 20:19 ` Evgeniy Polyakov

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=20090517223847.168d9ebd@nehalam \
    --to=shemminger@vyatta.com \
    --cc=clauder@accedian.com \
    --cc=ipng@69706e6720323030352d30312d31340a.nosense.org \
    --cc=netdev@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.