From: David Miller <davem@davemloft.net>
To: konrad.wilk@oracle.com
Cc: Ian.Campbell@citrix.com, mgorman@suse.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
xen-devel@lists.xensource.com, konrad@darnok.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] netvm: check for page == NULL when propogating the skb->pfmemalloc flag
Date: Thu, 30 Aug 2012 12:24:53 -0400 (EDT) [thread overview]
Message-ID: <20120830.122453.1449291050128191766.davem@davemloft.net> (raw)
In-Reply-To: <20120823141740.GA30305@phenom.dumpdata.com>
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Date: Thu, 23 Aug 2012 10:17:40 -0400
> On Wed, Aug 22, 2012 at 11:26:47AM +0100, Ian Campbell wrote:
>> On Wed, 2012-08-08 at 23:50 +0100, David Miller wrote:
>> > Just use something like a call to __pskb_pull_tail(skb, len) and all
>> > that other crap around that area can simply be deleted.
>>
>> I think you mean something like this, which works for me, although I've
>> only lightly tested it.
>>
>
> I've tested it heavily and works great.
>
> Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> and I took a look at it too and:
>
> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Applied, thanks everyone.
prev parent reply other threads:[~2012-08-30 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 8:55 [PATCH] netvm: check for page == NULL when propogating the skb->pfmemalloc flag Mel Gorman
2012-08-08 19:14 ` Rik van Riel
2012-08-08 22:50 ` David Miller
2012-08-13 10:26 ` Mel Gorman
2012-08-13 10:47 ` Mel Gorman
2012-08-13 18:56 ` Jeremy Fitzhardinge
2012-08-14 10:18 ` Mel Gorman
2012-08-13 15:41 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-08-14 10:05 ` Mel Gorman
2012-08-14 13:28 ` Konrad Rzeszutek Wilk
2012-08-22 10:26 ` Ian Campbell
2012-08-23 14:17 ` Konrad Rzeszutek Wilk
2012-08-30 16:24 ` 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=20120830.122453.1449291050128191766.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ian.Campbell@citrix.com \
--cc=akpm@linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=netdev@vger.kernel.org \
--cc=xen-devel@lists.xensource.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).