From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: eric.dumazet@gmail.com, nhorman@tuxdriver.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: packet: option to only pass skb protocol
Date: Tue, 5 Jan 2010 23:50:51 +0200 [thread overview]
Message-ID: <20100105215051.GD30921@redhat.com> (raw)
In-Reply-To: <20100105.134038.21223965.davem@davemloft.net>
On Tue, Jan 05, 2010 at 01:40:38PM -0800, David Miller wrote:
> From: "Michael S. Tsirkin" <mst@redhat.com>
> Date: Tue, 5 Jan 2010 22:50:40 +0200
>
> > binding socket to device might be done by a separate process
> > from the one doing sendmsg, and IMO the device socket is bound
> > to might change at any time.
> >
> > So the sending process would need to get socket name before
> > each sendmsg.
> >
> > Makes sense?
>
> Not really, when it's at the expense of everyone else.
>
> If you can pass the FD around, you can pass around auxiliary
> information as well.
>
> Make sense? :-)
At some level, of course I can. But I would have to do this
communication each time socket is bound to another device, as opposed to
passing the fd once. At least for me, option to autodetect protocol
would work even better though - it's what I do in the application
anyway.
--
MST
next prev parent reply other threads:[~2010-01-05 21:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 18:57 [PATCH] net: packet: option to only pass skb protocol Michael S. Tsirkin
2010-01-05 19:27 ` Eric Dumazet
2010-01-05 20:50 ` Michael S. Tsirkin
2010-01-05 21:40 ` David Miller
2010-01-05 21:50 ` Michael S. Tsirkin [this message]
2010-01-05 21:28 ` Chris Friesen
2010-01-05 21:42 ` David Miller
2010-01-05 21:45 ` Michael S. Tsirkin
2010-01-05 22:05 ` Michael S. Tsirkin
2010-01-05 22:13 ` Chris Friesen
2010-01-05 22:27 ` Michael S. Tsirkin
2010-01-05 23:51 ` David Miller
2010-01-06 9:12 ` Michael S. Tsirkin
2010-01-06 19:24 ` Michael S. Tsirkin
2010-01-07 8:27 ` Michał Mirosław
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=20100105215051.GD30921@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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).