From: Eric Dumazet <eric.dumazet@gmail.com>
To: Emanuele <e.emanuelegiuseppe@gmail.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: dev_loopback_xmit parameters
Date: Mon, 23 Apr 2018 15:36:03 -0700 [thread overview]
Message-ID: <c91f52c8-c7de-e555-a184-b62d39665b9f@gmail.com> (raw)
In-Reply-To: <eb1bf67b-7f38-a3b5-4974-6ee1d198887f@gmail.com>
On 04/23/2018 02:40 PM, Emanuele wrote:
> Hello,
>
> I don't know if this is the right place where to ask, but I was wondering why the dev_loopback_xmit function defined in /net/core/dev.c takes struct net * and struct sock * as parameters. They are never used, so I believe passing only the struct sk_buff * should be enough.
>
Look at net/ipv6/ip6_output.c where NF_HOOK() uses dev_loopback_xmit().
> In addition, it would like to know where I can read what is and how to set a skb dst_entry, since I don't really understand it.
>
> Thanks a lot,
>
> Emanuele
>
next prev parent reply other threads:[~2018-04-23 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 21:40 dev_loopback_xmit parameters Emanuele
2018-04-23 22:36 ` Eric Dumazet [this message]
2018-04-23 23:11 ` Emanuele
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=c91f52c8-c7de-e555-a184-b62d39665b9f@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=e.emanuelegiuseppe@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox