From: Ben Greear <greearb@candelatech•com>
To: "Michał Mirosław" <mirqus@gmail•com>
Cc: netdev@vger•kernel.org
Subject: Re: [PATCH 0/2] Allow NICs to pass Frame Checksum up the stack.
Date: Fri, 17 Jun 2011 13:48:03 -0700 [thread overview]
Message-ID: <4DFBBD83.9040300@candelatech.com> (raw)
In-Reply-To: <BANLkTikiNT1F39XaMFWc67OuP=StmntL=g@mail.gmail.com>
On 06/17/2011 01:00 PM, Michał Mirosław wrote:
> 2011/6/17<greearb@candelatech•com>:
>> From: Ben Greear<greearb@candelatech•com>
>>
>> This series provides ethtool support to set and get the rx-checksum
>> flag, and adds support to the e100 driver.
> [...]
>
> If you want to test the new features approach, you can shave top bit
> off NETIF_F_GSO_MASK (there are two unused bits there). The
> introducing patch will be +2 lines (+1 dev.c, +1 ethtool.c),
> implementation in e100: 20 lines less than patch you sent, ethtool
> userspace changes: none (assuming
> http://patchwork.ozlabs.org/patch/96374/ or equivalent applied).
Well, is that patch going in?
How do we get more bits if we need more than two? Totally new
API?
Thanks,
Ben
>
> Best Regards,
> Michał Mirosław
--
Ben Greear <greearb@candelatech•com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-06-17 20:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 19:40 [PATCH 0/2] Allow NICs to pass Frame Checksum up the stack greearb
2011-06-17 19:40 ` [PATCH 1/2] net: Support getting/setting RX-FCS in drivers greearb
2011-06-17 19:40 ` [PATCH 2/2] e100: Support receiving Ethernet FCS greearb
2011-06-18 1:47 ` Jeff Kirsher
2011-06-17 20:00 ` [PATCH 0/2] Allow NICs to pass Frame Checksum up the stack Michał Mirosław
2011-06-17 20:48 ` Ben Greear [this message]
2011-06-17 20:57 ` Ben Hutchings
2011-06-17 20:58 ` Ben Greear
2011-06-19 23:21 ` David Miller
2011-06-19 23:51 ` Ben Greear
2011-06-19 23:54 ` David Miller
2011-06-19 23:58 ` Ben Greear
2011-06-19 23:20 ` David Miller
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=4DFBBD83.9040300@candelatech.com \
--to=greearb@candelatech$(echo .)com \
--cc=mirqus@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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