From: David Miller <davem@davemloft.net>
To: sfeldma@gmail.com
Cc: netdev@vger.kernel.org, jiri@resnulli.us,
simon.horman@netronome.com, makita.toshiaki@lab.ntt.co.jp
Subject: Re: [PATCH net-next 0/5] rocker: revert back to support for nowait processes
Date: Mon, 15 Jun 2015 16:07:13 -0700 (PDT) [thread overview]
Message-ID: <20150615.160713.1499408328026540947.davem@davemloft.net> (raw)
In-Reply-To: <1434170150-63838-1-git-send-email-sfeldma@gmail.com>
From: sfeldma@gmail.com
Date: Fri, 12 Jun 2015 21:35:45 -0700
> One of the items removed from the rocker driver in the Spring Cleanup patch
> series was the ability to mark processing in the driver as "no wait" for
> those contexts where we cannot sleep. Turns out, we have "no wait"
> contexts where we want to program the device and we don't want to defer the
> processing to a process context. So re-add the ROCKER_OP_FLAG_NOWAIT flag
> to mark such processes, and propagate flags to mem allocator and to the
> device cmd executor. With NOWAIT, mem allocs are GFP_ATOMIC and device
> cmds are queued to the device, but the driver will not wait (sleep) for the
> response back from the device.
>
> My bad for removing NOWAIT support in the first place; I thought we could
> swing non-sleep contexts to process context using a work queue, for
> example, but there is push-back to keep processing in original context.
Series applied, thanks Scott.
prev parent reply other threads:[~2015-06-15 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 4:35 [PATCH net-next 0/5] rocker: revert back to support for nowait processes sfeldma
2015-06-13 4:35 ` [PATCH net-next 1/5] " sfeldma
2015-06-13 4:35 ` [PATCH net-next 2/5] rocker: mark neigh update event processing as 'no wait' sfeldma
2015-06-13 4:35 ` [PATCH net-next 3/5] rocker: mark STP update as 'no wait' processing sfeldma
2015-06-13 4:35 ` [PATCH net-next 4/5] rocker: move MAC learn event back to " sfeldma
2015-06-13 4:35 ` [PATCH net-next 5/5] rocker: move port stop " sfeldma
2015-06-15 23:07 ` David Miller [this message]
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=20150615.160713.1499408328026540947.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=netdev@vger.kernel.org \
--cc=sfeldma@gmail.com \
--cc=simon.horman@netronome.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).