From: Jiri Pirko <jiri@resnulli.us>
To: Andrew Lunn <andrew@lunn.ch>
Cc: John Ousterhout <ouster@cs.stanford.edu>,
Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org
Subject: Re: Upstream Homa?
Date: Sat, 12 Nov 2022 08:53:43 +0100 [thread overview]
Message-ID: <Y29RBxW69CtiML6I@nanopsycho> (raw)
In-Reply-To: <Y26huGkf50zPPCmf@lunn.ch>
Fri, Nov 11, 2022 at 08:25:44PM CET, andrew@lunn.ch wrote:
>On Fri, Nov 11, 2022 at 10:59:58AM -0800, John Ousterhout wrote:
>> The netlink and 32-bit kernel issues are new for me; I've done some digging to
>> learn more, but still have some questions.
>>
>
>> * Is the intent that netlink replaces *all* uses of /proc and ioctl? Homa
>> currently uses ioctls on sockets for I/O (its APIs aren't sockets-compatible).
Why exactly it isn't sockets-comatible?
>> It looks like switching to netlink would double the number of system calls that
>> have to be invoked, which would be unfortunate given Homa's goal of getting the
>> lowest possible latency. It also looks like netlink might be awkward for
>> dumping large volumes of kernel data to user space (potential for buffer
>> overflow?).
Netlink is slow, you should use it for fast path. It is for
configuration and stats.
next prev parent reply other threads:[~2022-11-12 7:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 19:42 Upstream Homa? John Ousterhout
2022-11-10 21:25 ` Stephen Hemminger
2022-11-10 23:23 ` Andrew Lunn
[not found] ` <CAGXJAmw=NY17=6TnDh0oV9WTmNkQCe9Q9F3Z=uGjG9x5NKn7TQ@mail.gmail.com>
2022-11-11 19:10 ` Stephen Hemminger
2022-11-11 19:25 ` Andrew Lunn
2022-11-12 7:53 ` Jiri Pirko [this message]
2022-11-13 6:25 ` John Ousterhout
2022-11-13 17:10 ` Andrew Lunn
2022-11-13 20:10 ` John Ousterhout
2022-11-13 20:37 ` Andrew Lunn
2022-11-14 5:37 ` John Ousterhout
2022-11-13 6:09 ` John Ousterhout
2022-11-13 8:24 ` Jiri Pirko
2022-11-13 18:53 ` Andrew Lunn
2022-12-04 18:17 ` Jamal Hadi Salim
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=Y29RBxW69CtiML6I@nanopsycho \
--to=jiri@resnulli.us \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=ouster@cs.stanford.edu \
--cc=stephen@networkplumber.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 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.