From: David Newall <davidn@davidnewall•com>
To: Lorenzo Colitti <lorenzo@google•com>, netdev@vger•kernel.org
Cc: hannes@stressinduktion•org, davem@davemloft•net, jpa@google•com
Subject: Re: [RFC net-next 0/4] Support UID range routing.
Date: Sat, 26 Apr 2014 22:44:49 +0930 [thread overview]
Message-ID: <535BB149.3090901@davidnewall.com> (raw)
In-Reply-To: <1398487705-13430-1-git-send-email-lorenzo@google.com>
Hi Lorenzo,
> In some environments it is useful to route packets differently
> based on the user ID.
I don't understand what your patch will do because, as I understand the
word, "routing" means forwarding a packet one hop closer to the
destination, so I expect you must reach the destination before you could
know the UID. I'm probably missing something quite obvious. Could you
illustrate a use-case?
Thanks,
David
next prev parent reply other threads:[~2014-04-26 13:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 4:48 [RFC net-next 0/4] Support UID range routing Lorenzo Colitti
2014-04-26 4:48 ` [RFC net-next 1/4] net: ipv6: Introduce flowi6_init_output Lorenzo Colitti
2014-04-26 5:56 ` Julian Anastasov
2014-04-27 4:03 ` Lorenzo Colitti
2014-04-28 7:07 ` Julian Anastasov
2014-04-26 4:48 ` [RFC net-next 2/4] net: core: Add a UID range to fib rules Lorenzo Colitti
2014-04-26 4:48 ` [RFC net-next 3/4] net: core: Add the UID to flowi[46]_init_output Lorenzo Colitti
2014-04-26 4:48 ` [RFC net-next 4/4] net: core: Add a RTA_UID attribute to routes Lorenzo Colitti
2014-04-26 13:14 ` David Newall [this message]
2014-04-28 14:38 ` [RFC net-next 0/4] Support UID range routing Lorenzo Colitti
[not found] ` <20140428.125807.409036177577836732.davem@davemloft.net>
2014-04-28 19:01 ` Lorenzo Colitti
2014-05-02 19:15 ` Lorenzo Colitti
2014-05-02 19:24 ` David Miller
2014-05-07 3:59 ` Lorenzo Colitti
2014-05-07 9:24 ` Hannes Frederic Sowa
2014-05-07 10:58 ` Lorenzo Colitti
2014-05-11 21:45 ` Hannes Frederic Sowa
2014-05-12 20:25 ` Lorenzo Colitti
2014-04-30 4:36 ` Lorenzo Colitti
2014-04-30 7:52 ` David Newall
2014-04-30 8:04 ` Lorenzo Colitti
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=535BB149.3090901@davidnewall.com \
--to=davidn@davidnewall$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=hannes@stressinduktion$(echo .)org \
--cc=jpa@google$(echo .)com \
--cc=lorenzo@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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