Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1615545
| From | David Miller <davem@davemloft.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH net-next v4 1/2] New kernel function to get IP overhead on a socket. |
| Date | 2017-04-03 22:40 +0200 |
| Message-ID | <tsgVA-3k5-21@gated-at.bofh.it> (permalink) |
| References | <tomGe-2CL-27@gated-at.bofh.it> <toxih-239-1@gated-at.bofh.it> <tsgLT-3gI-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
From: "R. Parameswaran" <parameswaran.r7@gmail.com> Date: Mon, 3 Apr 2017 13:28:11 -0700 (PDT) > Can I take this to mean that we do need to factor in IP options in > the L2TP device MTU setup (i.e approach in the posted patch is okay)? > > If yes, please let me know if I can keep the socket IP option overhead > calculations in a generic function, or it would be better to move it back into > L2TP code? If the user creates and maintains this UDP socket, then yes we have to account for potential IP options.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH net-next v4 1/2] New kernel function to get IP overhead on a socket. "R. Parameswaran" <parameswaran.r7@gmail.com> - 2017-04-03 22:30 +0200
Re: [PATCH net-next v4 1/2] New kernel function to get IP overhead on a socket. David Miller <davem@davemloft.net> - 2017-04-03 22:40 +0200
Re: [PATCH net-next v4 1/2] New kernel function to get IP overhead on a socket. David Miller <davem@davemloft.net> - 2017-04-04 04:20 +0200
Re: [PATCH net-next v4 1/2] New kernel function to get IP overhead on a socket. "R. Parameswaran" <parameswaran.r7@gmail.com> - 2017-04-04 04:20 +0200
csiph-web