From: David Miller <davem@davemloft.net>
To: dhowells@redhat.com
Cc: netdev@vger.kernel.org, linux-afs@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 00/10] rxrpc: Miscellaneous fixes
Date: Fri, 16 Sep 2016 01:55:10 -0400 (EDT)	[thread overview]
Message-ID: <20160916.015510.564823888003392258.davem@davemloft.net> (raw)
In-Reply-To: <147380525614.23135.7539695651371953351.stgit@warthog.procyon.org.uk>
From: David Howells <dhowells@redhat.com>
Date: Tue, 13 Sep 2016 23:20:56 +0100
> 
> Here's a set of miscellaneous fix patches.  There are a couple of points of
> note:
> 
>  (1) There is one non-fix patch that adjusts the call ref tracking
>      tracepoint to make kernel API-held refs on calls more obvious.  This
>      is a prerequisite for the patch that fixes prealloc refcounting.
> 
>  (2) The final patch alters how jumbo packets that partially exceed the
>      receive window are handled.  Previously, space was being left in the
>      Rx buffer for them, but this significantly hurts performance as the Rx
>      window can't be increased to match the OpenAFS Tx window size.
> 
>      Instead, the excess subpackets are discarded and an EXCEEDS_WINDOW ACK
>      is generated for the first.  To avoid the problem of someone trying to
>      run the kernel out of space by feeding the kernel a series of
>      overlapping maximal jumbo packets, we stop allowing jumbo packets on a
>      call if we encounter more than three jumbo packets with duplicate or
>      excessive subpackets.
 ...
> Tagged thusly:
> 
> 	git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> 	rxrpc-rewrite-20160913-1
Pulled, thanks David.
     prev parent reply	other threads:[~2016-09-16  5:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 22:20 [PATCH net-next 00/10] rxrpc: Miscellaneous fixes David Howells
2016-09-13 22:21 ` [PATCH net-next 01/10] rxrpc: Make sure we initialise the peer hash key David Howells
2016-09-13 22:21 ` [PATCH net-next 02/10] rxrpc: Add missing wakeup on Tx window rotation David Howells
2016-09-13 22:21 ` [PATCH net-next 03/10] rxrpc: The IDLE ACK packet should use rxrpc_idle_ack_delay David Howells
2016-09-13 22:21 ` [PATCH net-next 04/10] rxrpc: Requeue call for recvmsg if more data David Howells
2016-09-13 22:21 ` [PATCH net-next 05/10] rxrpc: Add missing unlock in rxrpc_call_accept() David Howells
2016-09-13 22:21 ` [PATCH net-next 06/10] rxrpc: Use skb->len not skb->data_len David Howells
2016-09-13 22:21 ` [PATCH net-next 07/10] rxrpc: Allow tx_winsize to grow in response to an ACK David Howells
2016-09-13 22:21 ` [PATCH net-next 08/10] rxrpc: Adjust the call ref tracepoint to show kernel API refs David Howells
2016-09-13 22:21 ` [PATCH net-next 09/10] rxrpc: Fix prealloc refcounting David Howells
2016-09-13 22:22 ` [PATCH net-next 10/10] rxrpc: Correctly initialise, limit and transmit call->rx_winsize David Howells
2016-09-16  5:55 ` David Miller [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=20160916.015510.564823888003392258.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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 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).