From: jamal <hadi@cyberus.ca>
To: San Mehat <san@google.com>
Cc: davem@davemloft.net, mst@redhat.com, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, digitaleric@google.com, mikew@google.com,
miche@google.com, maccarro@google.com
Subject: Re: [RFC 0/0] Introducing a generic socket offload framework
Date: Sat, 20 Aug 2011 10:32:35 -0400 [thread overview]
Message-ID: <1313850755.1734.724.camel@mojatatu> (raw)
In-Reply-To: <CAPi7mHp==JPA-0vNZ+xWRzOuJYUxsUL3UY=o=VtMUsB-YcFHwQ@mail.gmail.com>
On Fri, 2011-08-19 at 07:58 -0700, San Mehat wrote:
> Can you explain a good use-case for SOCK_RAW in this type of
> environment? We were noodling it around locally and couldn't come up
> with one that we needed to support.
One that comes to mind is the case of Samir's app: youd need to handle
some of the apps that ride on top of IP typically using SOCK_RAW
eg ping, OSPF essentially anything on IP that doesnt have transport
built into kernel etc;
> > Q: If you want this to be transparent to the apps, who/what is doing
> > the tagging of SOCK_HWASSIST? clearly not the app if you dont want to
> > change it.
>
> The decision of whether to tag a socket or not is made by the 'hardware'
As in some config interface?
cheers,
jamal
prev parent reply other threads:[~2011-08-20 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 22:07 [RFC 0/0] Introducing a generic socket offload framework San Mehat
2011-08-18 22:57 ` Alan Cox
2011-08-18 23:03 ` Alan Cox
2011-08-18 23:18 ` San Mehat
2011-08-19 9:28 ` Alan Cox
2011-08-19 3:39 ` David Miller
2011-08-19 12:49 ` jamal
2011-08-19 14:44 ` San Mehat
2011-08-19 14:58 ` San Mehat
2011-08-20 14:32 ` jamal [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=1313850755.1734.724.camel@mojatatu \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=digitaleric@google.com \
--cc=jhs@mojatatu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maccarro@google.com \
--cc=miche@google.com \
--cc=mikew@google.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=san@google.com \
--cc=virtualization@lists.linux-foundation.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).