All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Andi Kleen <andi@firstfloor.org>, Avi Kivity <avi@redhat.com>,
	Elad Lahav <elahav@uwaterloo.ca>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Implementation of the sendgroup() system call
Date: Mon, 4 May 2009 12:18:14 +0200	[thread overview]
Message-ID: <20090504101814.GG23223@one.firstfloor.org> (raw)
In-Reply-To: <49FEBBC9.9000708@cosmosbay.com>

On Mon, May 04, 2009 at 11:56:25AM +0200, Eric Dumazet wrote:
> Andi Kleen a écrit :
> 
> >>> Or perhaps simple send to a local multicast group and let
> >>> some netfilter module turn that into regular UDP.
> >>>  
> >> Sounds hacky and rooty.
> > 
> > rooty? Everyone can send to all directions anyways.
> > 
> > It wouldn't be perfect, but quite usable as a short term solution
> > for a production server.
> 
> Anyway, a netfilter module doesnt fit the needs (separate header/footer
> for each destination)

netfilter modues can create new skbs that reference the main data and replace 
the header.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2009-05-04 10:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04  1:40 [PATCH] Implementation of the sendgroup() system call Elad Lahav
2009-05-04  7:13 ` Andi Kleen
2009-05-04  7:30   ` Avi Kivity
2009-05-04  9:53     ` Andi Kleen
2009-05-04  9:56       ` Eric Dumazet
2009-05-04 10:18         ` Andi Kleen [this message]
2009-05-04  9:58       ` Avi Kivity
2009-05-04  7:42   ` Rémi Denis-Courmont
2009-05-04 13:44   ` Elad Lahav
2009-05-04 14:50     ` Andi Kleen
2009-05-05  0:24       ` Elad Lahav
2009-05-06 11:25       ` Tim Brecht
2009-05-04  7:43 ` Eric Dumazet
2009-05-04  9:03   ` Eric Dumazet
2009-05-04 13:32   ` Elad Lahav

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=20090504101814.GG23223@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=avi@redhat.com \
    --cc=dada1@cosmosbay.com \
    --cc=elahav@uwaterloo.ca \
    --cc=linux-kernel@vger.kernel.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.