From: Jason Xing <kerneljasonxing@gmail.com>
To: Juntong Deng <juntong.deng@outlook.com>
Cc: Eric Dumazet <edumazet@google.com>,
willemdebruijn.kernel@gmail.com, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net/packet: Add getsockopt support for PACKET_COPY_THRESH
Date: Fri, 8 Mar 2024 21:27:24 +0800 [thread overview]
Message-ID: <CAL+tcoAwPv7bquhmaUr_NckEfQbp2xuNNOSswtmxRHHVCiY9+A@mail.gmail.com> (raw)
In-Reply-To: <AM6PR03MB5848654CAA0174407FD4DE7299272@AM6PR03MB5848.eurprd03.prod.outlook.com>
On Fri, Mar 8, 2024 at 9:19 PM Juntong Deng <juntong.deng@outlook.com> wrote:
>
> On 2024/3/8 21:11, Jason Xing wrote:
> > On Fri, Mar 8, 2024 at 8:56 PM Eric Dumazet <edumazet@google.com> wrote:
> >>
> >> On Fri, Mar 8, 2024 at 1:43 PM Juntong Deng <juntong.deng@outlook.com> wrote:
> >>>
> >>> Currently getsockopt does not support PACKET_COPY_THRESH,
> >>> and we are unable to get the value of PACKET_COPY_THRESH
> >>> socket option through getsockopt.
> >>>
> >>> This patch adds getsockopt support for PACKET_COPY_THRESH.
> >>>
> >>> In addition, this patch converts access to copy_thresh to
> >>> READ_ONCE/WRITE_ONCE.
> >>>
> >>> Signed-off-by: Juntong Deng <juntong.deng@outlook.com>
> >>> ---
> >>> V1 -> V2: Use READ_ONCE/WRITE_ONCE.
> >>>
> >>> net/packet/af_packet.c | 7 +++++--
> >>> 1 file changed, 5 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/net/packet/af_packet.c b/net/packet/af_packet.c
> >>> index 0db31ca4982d..61270826b9ac 100644
> >>> --- a/net/packet/af_packet.c
> >>> +++ b/net/packet/af_packet.c
> >>> @@ -2318,7 +2318,7 @@ static int tpacket_rcv(struct sk_buff *skb, struct net_device *dev,
> >>> }
> >>> if (po->tp_version <= TPACKET_V2) {
> >>> if (macoff + snaplen > po->rx_ring.frame_size) {
> >>> - if (po->copy_thresh &&
> >>> + if (READ_ONCE(po->copy_thresh) &&
> >>> atomic_read(&sk->sk_rmem_alloc) < sk->sk_rcvbuf) {
> >>> if (skb_shared(skb)) {
> >>> copy_skb = skb_clone(skb, GFP_ATOMIC);
> >>> @@ -3836,7 +3836,7 @@ packet_setsockopt(struct socket *sock, int level, int optname, sockptr_t optval,
> >>> if (copy_from_sockptr(&val, optval, sizeof(val)))
> >>> return -EFAULT;
> >>>
> >>> - pkt_sk(sk)->copy_thresh = val;
> >>> + WRITE_ONCE(pkt_sk(sk)->copy_thresh, val);
> >>> return 0;
> >>> }
> >>> case PACKET_VERSION:
> >>> @@ -4090,6 +4090,9 @@ static int packet_getsockopt(struct socket *sock, int level, int optname,
> >>> case PACKET_VNET_HDR_SZ:
> >>> val = READ_ONCE(po->vnet_hdr_sz);
> >>> break;
> >>> + case PACKET_COPY_THRESH:
> >>> + val = READ_ONCE(pkt_sk(sk)->copy_thresh);
> >>> + break;
> >>> case PACKET_VERSION:
> >>> val = po->tp_version;
> >>> break;
> >>> --
> >>> 2.39.2
> >>>
> >>
> >> I think you forgot to change net/packet/diag.c pdiag_put_info()
> >>
> >
> > Ah, he updated his patch so soon even without taking a break.
> >
> > I just replied to the v1 thread with three changes made.
> >
> > Juntong, you could check your v1 patch thread and you will see the
> > missing point.
> >
> > Thanks,
> > Jason
>
> Hi Jason,
>
> Thanks, I have fixed this in the v3 patch.
The patch itself looks good to me.
But next time please do not post the patch too often, you have to wait
around 24 hour at least. We need to obey the rule. Then you have
plenty of time to collect/rethink about those suggestions...
Thanks,
Jason
prev parent reply other threads:[~2024-03-08 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 12:42 [PATCH net-next v2] net/packet: Add getsockopt support for PACKET_COPY_THRESH Juntong Deng
2024-03-08 12:56 ` Eric Dumazet
2024-03-08 13:11 ` Jason Xing
2024-03-08 13:19 ` Juntong Deng
2024-03-08 13:27 ` Jason Xing [this message]
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=CAL+tcoAwPv7bquhmaUr_NckEfQbp2xuNNOSswtmxRHHVCiY9+A@mail.gmail.com \
--to=kerneljasonxing@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=juntong.deng@outlook.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).