From: Wedson Almeida Filho
Date: Mon, 24 Jun 2013 15:47:18 -0700
> The summary line of the original commit is "[NET]: Zerocopy sequential
> reading of skb data".
He's telling you to put this in the commit message, and resubmit
the patch.
--
To unsubscribe from this list: send the line
Hello.
On 06/25/2013 02:47 AM, Wedson Almeida Filho wrote:
The summary line of the original commit is "[NET]: Zerocopy sequential
reading of skb data".
That's interesting but please update your patch.
WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
The summary line of the original commit is "[NET]: Zerocopy sequential
reading of skb data".
On Mon, Jun 24, 2013 at 3:35 AM, Sergei Shtylyov
wrote:
> Hello.
>
>
> On 24-06-2013 10:33, Wedson Almeida Filho wrote:
>
>> Callers of skb_seq_read() are currently forced to call
>> skb_abort_seq_read()
Hello.
On 24-06-2013 10:33, Wedson Almeida Filho wrote:
Callers of skb_seq_read() are currently forced to call skb_abort_seq_read()
even when consuming all the data because the last call to skb_seq_read (the
one that returns 0 to indicate the end) fails to unmap the last fragment page.
With
From: Wedson Almeida Filho
Date: Sun, 23 Jun 2013 23:33:48 -0700
> Callers of skb_seq_read() are currently forced to call skb_abort_seq_read()
> even when consuming all the data because the last call to skb_seq_read (the
> one that returns 0 to indicate the end) fails to unmap the last fragment
Callers of skb_seq_read() are currently forced to call skb_abort_seq_read()
even when consuming all the data because the last call to skb_seq_read (the
one that returns 0 to indicate the end) fails to unmap the last fragment page.
With this patch callers will be allowed to traverse the SKB data
Callers of skb_seq_read() are currently forced to call skb_abort_seq_read()
even when consuming all the data because the last call to skb_seq_read (the
one that returns 0 to indicate the end) fails to unmap the last fragment page.
With this patch callers will be allowed to traverse the SKB data
From: Wedson Almeida Filho wedso...@gmail.com
Date: Sun, 23 Jun 2013 23:33:48 -0700
Callers of skb_seq_read() are currently forced to call skb_abort_seq_read()
even when consuming all the data because the last call to skb_seq_read (the
one that returns 0 to indicate the end) fails to unmap the
Hello.
On 24-06-2013 10:33, Wedson Almeida Filho wrote:
Callers of skb_seq_read() are currently forced to call skb_abort_seq_read()
even when consuming all the data because the last call to skb_seq_read (the
one that returns 0 to indicate the end) fails to unmap the last fragment page.
With
The summary line of the original commit is [NET]: Zerocopy sequential
reading of skb data.
On Mon, Jun 24, 2013 at 3:35 AM, Sergei Shtylyov
sergei.shtyl...@cogentembedded.com wrote:
Hello.
On 24-06-2013 10:33, Wedson Almeida Filho wrote:
Callers of skb_seq_read() are currently forced to
Hello.
On 06/25/2013 02:47 AM, Wedson Almeida Filho wrote:
The summary line of the original commit is [NET]: Zerocopy sequential
reading of skb data.
That's interesting but please update your patch.
WBR, Sergei
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
From: Wedson Almeida Filho wedso...@gmail.com
Date: Mon, 24 Jun 2013 15:47:18 -0700
The summary line of the original commit is [NET]: Zerocopy sequential
reading of skb data.
He's telling you to put this in the commit message, and resubmit
the patch.
--
To unsubscribe from this list: send the
12 matches
Mail list logo
