From: David Riddoch <driddoch@solarflare.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: "Jörn Engel" <joern@logfs.org>,
linux-mtd@lists.infradead.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH] [MTD] [RFC] New Solarflare NIC EEPROM/Flash driver
Date: Sun, 13 Jan 2008 17:19:33 +0000 [thread overview]
Message-ID: <478A4825.8000006@solarflare.com> (raw)
In-Reply-To: <20080111185550.GN3544@solarflare.com>
Ben Hutchings wrote:
>>>> struct semaphore access_lock; should become a mutex.
>>>>
>>> Right. We've tended to be quite conservative in using newer kernel
>>> features, since we also need to support old kernels, but we have a
>>> good backward-compatibility layer now (unifdef'd out of the submitted
>>> code) so this shouldn't be a problem.
>>>
>> Ok. A straight conversion to a mutex will likely cause trouble with
>> your reset routine. Not sure what to do here.
>>
>
> We can use a mutex if the net driver is guaranteed to call
> reset_suspend() and reset_resume() in the same context. This is
> currently true (they are always called in a pair by efx_reset() in
> efx.c) but I'm not sure we want to guarantee that.
>
reset_suspend() is documented as being called in a context that permits
sleeping, and I can't see us ever changing that. reset_resume() will
also continue to permit sleeping (although that isn't currently documented).
Cheers,
David
--
David Riddoch +++ Solarflare +++ driddoch@solarflare.com
next prev parent reply other threads:[~2008-01-13 17:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 18:51 [PATCH] [MTD] [RFC] New Solarflare NIC EEPROM/Flash driver Robert Stonehouse
2008-01-10 20:13 ` Jörn Engel
2008-01-10 23:16 ` Jörn Engel
2008-01-11 12:50 ` Ben Hutchings
2008-01-11 13:24 ` Jörn Engel
2008-01-11 18:55 ` Ben Hutchings
2008-01-11 19:57 ` Jörn Engel
2008-01-13 17:19 ` David Riddoch [this message]
2008-01-14 17:04 ` [PATCH] [MTD] [RFC] New Solarflare NIC EEPROM/Flash driver (2nd try) Ben Hutchings
2008-01-15 16:46 ` Jörn Engel
2008-01-15 17:35 ` Ben Hutchings
2008-01-15 17:55 ` Jörn Engel
2008-01-15 17:57 ` Ben Hutchings
2008-01-15 18:28 ` Jörn Engel
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=478A4825.8000006@solarflare.com \
--to=driddoch@solarflare.com \
--cc=bhutchings@solarflare.com \
--cc=joern@logfs.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-net-drivers@solarflare.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