From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Kirill Tkhai <ktkhai@virtuozzo.com>
Cc: santosh.shilimkar@oracle.com, davem@davemloft.net,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
rds-devel@oss.oracle.com, edumazet@google.com
Subject: Re: [PATCH RFC RFC] rds: Use NETDEV_UNREGISTER in rds_tcp_dev_event() (then kill NETDEV_UNREGISTER_FINAL)
Date: Fri, 16 Mar 2018 14:31:33 -0400 [thread overview]
Message-ID: <20180316183133.GP16870@oracle.com> (raw)
In-Reply-To: <82d6e954-8043-078c-266c-2f1ac992f864@virtuozzo.com>
On (03/16/18 21:14), Kirill Tkhai wrote:
>
> I did the second version and sent you. Have you tried it?
I tried it briefly, and it works for the handful of testcases
that I tried, but I still think its very werid to register
as both a device and a subsys, esp in the light of the
warning in net_namespace.h
Thus I have to spend some time reviewing your patch,
and I cannot give you an answer in the next 5 minutes.
> Calling netdevice handler for every event is more disturbing,
> as number of events is several times bigger, than one more
> pernet exit method.
So you are saying there are scaling constraints on subsystems
that register for netdevice handlers. The disturbing part
of that is that it does not scale.
Thanks.
--Sowmini
next prev parent reply other threads:[~2018-03-16 18:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 12:38 [PATCH RFC RFC] rds: Use NETDEV_UNREGISTER in rds_tcp_dev_event() (then kill NETDEV_UNREGISTER_FINAL) Kirill Tkhai
2018-03-16 13:00 ` Sowmini Varadhan
2018-03-16 13:17 ` Kirill Tkhai
2018-03-16 13:53 ` Sowmini Varadhan
2018-03-16 14:36 ` Kirill Tkhai
2018-03-16 14:41 ` Kirill Tkhai
2018-03-16 17:29 ` Sowmini Varadhan
2018-03-16 18:14 ` Kirill Tkhai
2018-03-16 18:31 ` Sowmini Varadhan [this message]
2018-03-16 18:48 ` Kirill Tkhai
2018-03-16 18:53 ` Sowmini Varadhan
2018-03-17 14:15 ` Sowmini Varadhan
2018-03-17 21:13 ` Kirill Tkhai
2018-03-17 21:26 ` [rds-devel] " Sowmini Varadhan
2018-03-17 21:55 ` Kirill Tkhai
2018-03-18 20:45 ` Sowmini Varadhan
2018-03-19 10:08 ` Kirill Tkhai
2018-03-20 11:37 ` Håkon Bugge
2018-03-20 13:29 ` Sowmini Varadhan
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=20180316183133.GP16870@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.