From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] [PRE-RFC 4/6] mptcp: queue data for mptcp level retransmission
Date: Mon, 19 Aug 2019 13:12:28 +0200 [thread overview]
Message-ID: <20190819111228.GE2588@breakpoint.cc> (raw)
In-Reply-To: 666fcde927e49fe2e51ebf38e8b6b7d2c3da13d2.1565970525.git.pabeni@redhat.com
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
Paolo Abeni <pabeni(a)redhat.com> wrote:
> keep the send page fragment on an MPTCP level retransmission queue.
> the queue entries are allocated inside the page frag allocator,
> acquiring an additional reference to the page for each list entry.
>
> Also switch to a custom page frag refill function, to ensure that
> the current page fragment can always host an MPTCP rtx queue entry.
>
> The MPTCP rtx queue is flushed at socket destroy() time.
> +/* ensure we get enough memory for the frag hdr, beyond some minimal amount of
> + * data
> + */
> +bool mptcp_page_frag_refill(struct sock *sk, struct page_frag *pfrag)
> +{
> + if (likely(skb_page_frag_refill(32U + sizeof(struct mptcp_data_frag),
> + pfrag, sk->sk_allocation)))
Where is that 32U coming from?
> +static inline struct mptcp_data_frag *
> +mptcp_carve_data_frag(const struct mptcp_sock *msk, struct page_frag *pfrag,
> + int offset)
> +{
> + struct mptcp_data_frag *dfrag;
> +
> + offset = ALIGN(offset, BITS_PER_LONG / 8);
sizeof(long)?
The concept of keeping page frags for rexmit looks good to me, thanks Paolo
for working on this.
next reply other threads:[~2019-08-19 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 11:12 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-19 12:46 [MPTCP] [PRE-RFC 4/6] mptcp: queue data for mptcp level retransmission Paolo Abeni
2019-08-16 16:48 Paolo Abeni
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=20190819111228.GE2588@breakpoint.cc \
--to=unknown@example.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.