From: Nicola Padovano <nicola.padovano@gmail.com>
To: AIJAZ BAIG <aijazbaig1@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
netfilter-devel <netfilter-devel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: problem with flowi structure
Date: Fri, 17 Sep 2010 10:46:10 +0200 [thread overview]
Message-ID: <AANLkTimpnqNSE21u=2qjb5VGJrn_3_--Bqp4veCNXMPE@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim7TeMCG9RQyrrk8WS4+S_y1q06+8FG2-X=1cB-@mail.gmail.com>
Aijaz, great! Now it' clear. Thank you.
It remains a problem: the meaning of
fl.nl_u.ip4_u.saddr = 0
But, first of all:
- we know that a routing table doesn't contain the ip source
- but the routing cache contains it.
so my first question is: why routing cache has it and routing cache
not? what it its usage?
Then my second question: the meaning of fl.nl_u.ip4_u.saddr = 0
thank you very much
On Fri, Sep 17, 2010 at 7:40 AM, AIJAZ BAIG <aijazbaig1@gmail.com> wrote:
> Hi there,
>
> Well..if u see the code, ull see that ip_route_output_key is a wrapper
> around ip_route_output_flow which in turn internally calls
> __ip_route_output_key. This later function tries to find a route for a
> packet first by looking up the routing cache and then if it isnt found
> there it constructs a cache entry by calling its slow counterpart
> which is ip_route_output_slow.
>
> Now, the name tells u a lot. First ip_route_output_key tells u that
> this function 'routes' an 'output' packet. An output packet normally
> means that the packet is a locally generated packet. The routing (L3)
> protocol being used is ip (ipv4 specifically) and key tells us that we
> are specifying the key to be used to check the routing cache (since
> the cache is organized as a hash and it needs a key to retrieve an
> entry).
>
> Thus all in all, the ip_route_output_key function is used to get a
> route for an output packet either from the routing cache if an entry
> is present or create one and update the cache accordingly.
>
> Hope it helped.
>
> Regards,
> Aijaz
>
> On 9/17/10, Nicola Padovano <nicola.padovano@gmail.com> wrote:
>> ok, let's step back...
>> what's the task of ip_route_output_key function ?
>>
>> --
>> Nicola Padovano
>> e-mail: nicola.padovano@gmail.com
>> web: http://npadovano.altervista.org
>> --
>> To unsubscribe from this list: send the line "unsubscribe netfilter-devel"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
--
Nicola Padovano
e-mail: nicola.padovano@gmail.com
web: http://npadovano.altervista.org
next prev parent reply other threads:[~2010-09-17 8:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 15:14 problem with flowi structure Nicola Padovano
2010-09-16 15:26 ` Eric Dumazet
2010-09-16 15:30 ` Nicola Padovano
2010-09-16 15:54 ` Eric Dumazet
2010-09-16 19:25 ` Nicola Padovano
2010-09-17 5:40 ` AIJAZ BAIG
2010-09-17 8:46 ` Nicola Padovano [this message]
2010-09-17 9:08 ` Eric Dumazet
2010-09-17 9:53 ` Nicola Padovano
2010-09-17 16:27 ` Nicola Padovano
2010-09-17 16:34 ` Eric Dumazet
2010-09-17 17:05 ` Nicola Padovano
2010-09-17 17:51 ` Eric Dumazet
2010-09-17 18:01 ` Nicola Padovano
2010-09-17 18:07 ` Eric Dumazet
2010-09-17 18:25 ` Nicola Padovano
2010-10-01 23:46 ` Jan Engelhardt
2010-10-02 8:08 ` Nicola Padovano
2010-10-02 20:18 ` David Miller
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='AANLkTimpnqNSE21u=2qjb5VGJrn_3_--Bqp4veCNXMPE@mail.gmail.com' \
--to=nicola.padovano@gmail.com \
--cc=aijazbaig1@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).