[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130709.214156.1738814737075691376.davem@davemloft.net>
Date: Tue, 09 Jul 2013 21:41:56 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: eliezer.tamir@...ux.intel.com
Cc: corbet@....net, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, dwmw2@...radead.org,
eliezer@...ir.org.il
Subject: Re: [PATCH net-next] net: rename low latency sockets functions to
busy poll
From: Eliezer Tamir <eliezer.tamir@...ux.intel.com>
Date: Wed, 10 Jul 2013 06:29:16 +0300
> If the following names changes are acceptable I will try to send out
> a patch today.
>
> 1. include/net/ll_poll.h -> include/net/busy_poll.h
Agreed.
> 2. ndo_ll_poll -> ndo_busy_poll
>
> - not technically accurate since the ndo callback does not itself busy
> poll, it's just used to implement it.
I think this name change is accurate, it expresses the two elements of
what it does. It's busy waiting, in that it's doing a synchronous
scan of the device's RX queue, and it's polling just like NAPI polling
does.
> maybe ndo_napi_id_poll? or ndo_id_poll? I don't really like any of them,
> so a suggestion would be nice.
This would make it sound like it's some new version of the existing
NAPI poll.
Well... what would be great would be to come up with some single
interface that drivers can implement rather than having to have
both napi->poll and netdevice_ops->ndo_ll_poll(). But that's a task
for a later date.
Therefore, ndo_busy_poll is probably best for now.
> 3. sysctl_net_ll_{read,poll} -> sysctl_net_busy_{read,poll}
> - along with matching file name changes.
Agreed.
> 4. {sk,skb}_mark_ll -> {sk,skb}_mark_napi_id
Agreed.
> 5. LL_SO -> BUSY_POLL_SO
Agreed.
> Did I miss anything?
Nope, looks complete. And also do the manpage update.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists