[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180308.112553.749777250006660851.davem@davemloft.net>
Date: Thu, 08 Mar 2018 11:25:53 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: mlichvar@...hat.com
Cc: eric.dumazet@...il.com, jesus.sanchez-palencia@...el.com,
netdev@...r.kernel.org, jhs@...atatu.com, xiyou.wangcong@...il.com,
jiri@...nulli.us, vinicius.gomes@...el.com,
richardcochran@...il.com, intel-wired-lan@...ts.osuosl.org,
anna-maria@...utronix.de, henrik@...tad.us, tglx@...utronix.de,
john.stultz@...aro.org, levi.pearson@...man.com,
edumazet@...gle.com, willemb@...gle.com
Subject: Re: [RFC v3 net-next 08/18] net: SO_TXTIME: Add clockid and
drop_if_late params
From: Miroslav Lichvar <mlichvar@...hat.com>
Date: Thu, 8 Mar 2018 12:37:22 +0100
> Well, I'd not expect it to be a common use case, but a public NTP
> server could be sending millions of packets per second in traffic
> peaks (typically at *:00:00) over multiple interfaces.
That's the problem.
Bloating up sk_buff for an uncommon use case, penalizing all others,
is a non-starter.
Sorry.
Powered by blists - more mailing lists