All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Chaitanya T K <chaitanya.mgit@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] cfg80211: Don't re-use the skb for larger NL messages.
Date: Sun, 31 May 2015 10:31:32 +0200	[thread overview]
Message-ID: <1433061092.2370.1.camel@sipsolutions.net> (raw)
In-Reply-To: <1433028494-9665-1-git-send-email-chaitanya.mgit@gmail.com> (sfid-20150531_012825_827034_87A26BAD)

On Sun, 2015-05-31 at 04:58 +0530, Chaitanya T K wrote:
> cfg80211 reuses the skb before asking for a fresh on from genl framework, 
> this works efficiently for smaller messages but NLM_F_DUMP is normally 
> used to transport larger data normally > PAGE_SIZE, so if the message 
> occupies more than GOODSIZE its better to ask for a new, saves couple
> of hanshakes with the driver.
> 
> This improves the time to get the DUMP response across to user space.

This doesn't make any sense. If the driver is slow to actually create
the data, it should implement this logic, but realistically the driver
should just check if there's enough space and only try to create data to
put into the skb if it's sufficient?

It sounds to me like you're actually interacting with the hardware at
this point (otherwise it wouldn't be slow!) which pretty much seems
wrong anyway.

johannes


  parent reply	other threads:[~2015-05-31  8:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-30 23:28 [PATCH v2] cfg80211: Don't re-use the skb for larger NL messages Chaitanya T K
2015-05-31  6:58 ` Arend van Spriel
2015-05-31  9:56   ` Krishna Chaitanya
2015-05-31  8:31 ` Johannes Berg [this message]
2015-05-31 10:01   ` Krishna Chaitanya
2015-05-31 10:42     ` Johannes Berg
2015-05-31 11:17       ` Krishna Chaitanya
2015-05-31 11:21         ` Johannes Berg
2015-05-31 11:39           ` Krishna Chaitanya

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=1433061092.2370.1.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=chaitanya.mgit@gmail.com \
    --cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.