From: Saeed Mahameed <saeed@kernel.org>
To: David Awogbemila <awogbemila@google.com>, netdev@vger.kernel.org
Cc: Catherine Sullivan <csully@google.com>,
Yangchun Fu <yangchun@google.com>
Subject: Re: [PATCH net-next v7 1/4] gve: Add support for raw addressing device option
Date: Thu, 19 Nov 2020 12:21:15 -0800 [thread overview]
Message-ID: <9b38c47593d2dedd5cad2c425b778a60cc7eeedf.camel@kernel.org> (raw)
In-Reply-To: <20201118232014.2910642-2-awogbemila@google.com>
On Wed, 2020-11-18 at 15:20 -0800, David Awogbemila wrote:
> From: Catherine Sullivan <csully@google.com>
>
> Add support to describe device for parsing device options. As
> the first device option, add raw addressing.
>
> "Raw Addressing" mode (as opposed to the current "qpl" mode) is an
> operational mode which allows the driver avoid bounce buffer copies
> which it currently performs using pre-allocated qpls
> (queue_page_lists)
> when sending and receiving packets.
> For egress packets, the provided skb data addresses will be
> dma_map'ed and
> passed to the device, allowing the NIC can perform DMA directly - the
> driver will not have to copy the buffer content into pre-allocated
> buffers/qpls (as in qpl mode).
> For ingress packets, copies are also eliminated as buffers are handed
> to
> the networking stack and then recycled or re-allocated as
> necessary, avoiding the use of skb_copy_to_linear_data().
>
> This patch only introduces the option to the driver.
> Subsequent patches will add the ingress and egress functionality.
>
> Reviewed-by: Yangchun Fu <yangchun@google.com>
> Signed-off-by: Catherine Sullivan <csully@google.com>
> Signed-off-by: David Awogbemila <awogbemila@google.com>
> ---
>
...
> diff --git a/drivers/net/ethernet/google/gve/gve_adminq.c
> b/drivers/net/ethernet/google/gve/gve_adminq.c
> index 24ae6a28a806..1e2d407cb9d2 100644
> --- a/drivers/net/ethernet/google/gve/gve_adminq.c
> +++ b/drivers/net/ethernet/google/gve/gve_adminq.c
> @@ -14,6 +14,57 @@
> #define GVE_ADMINQ_SLEEP_LEN 20
> #define GVE_MAX_ADMINQ_EVENT_COUNTER_CHECK 100
>
> +#define GVE_DEVICE_OPTION_ERROR_FMT "%s option error:\n" \
> +"Expected: length=%d, feature_mask=%x.\n" \
> +"Actual: length=%d, feature_mask=%x.\n"
> +
> +static inline
> +struct gve_device_option *gve_get_next_option(struct
>
Following Dave's policy, no static inline functions in C files.
This is control path so you don't really need the inline here.
next prev parent reply other threads:[~2020-11-19 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 23:20 [PATCH net-next v7 0/4] GVE Raw Addressing David Awogbemila
2020-11-18 23:20 ` [PATCH net-next v7 1/4] gve: Add support for raw addressing device option David Awogbemila
2020-11-19 20:21 ` Saeed Mahameed [this message]
2020-11-20 0:22 ` David Awogbemila
2020-11-20 2:01 ` Maciej Fijalkowski
2020-11-20 5:07 ` David Awogbemila
2020-11-18 23:20 ` [PATCH net-next v7 2/4] gve: Add support for raw addressing to the rx path David Awogbemila
2020-11-18 23:20 ` [PATCH net-next v7 3/4] gve: Rx Buffer Recycling David Awogbemila
2020-11-18 23:20 ` [PATCH net-next v7 4/4] gve: Add support for raw addressing in the tx path David Awogbemila
2020-11-19 16:48 ` [PATCH net-next v7 0/4] GVE Raw Addressing Jakub Kicinski
2020-11-19 16:56 ` Alexander Duyck
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=9b38c47593d2dedd5cad2c425b778a60cc7eeedf.camel@kernel.org \
--to=saeed@kernel.org \
--cc=awogbemila@google.com \
--cc=csully@google.com \
--cc=netdev@vger.kernel.org \
--cc=yangchun@google.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).