From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Rasesh Mody <rmody@brocade.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
jesse.brandeburg@intel.com, "Ronciak,
John" <john.ronciak@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [RFC 0/7] Fixing dma mask setting in various network drivers
Date: Tue, 11 Jun 2013 16:50:44 -0700 [thread overview]
Message-ID: <20130611165044.00000d3a@unknown> (raw)
In-Reply-To: <20130611203505.GO18614@n2100.arm.linux.org.uk>
On Tue, 11 Jun 2013 13:35:05 -0700
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> As part of my review of all this stuff, I'm wondering whether a helper
> to set both masks makes sense. Something like:
>
> static inline int dma_set_masks(struct device *dev, u64 mask)
it doesn't need to be inline, it is never called in hotpath.
> {
> int ret = dma_set_mask(dev, mask);
> if (ret == 0)
> dma_set_coherent_mask(dev, mask);
> return ret;
> }
>
> "dma_set_masks()" is a little too close to dma_set_mask() though; and
how about dma_set_mask_and_coherent(...)
> such a function looks like it would be usable for 20 odd drivers
> currently. The plus point is that it may help to prevent this kind
> of issue in the future...
>
> Thoughts?
I really like the idea of consolidating this in the kernel with a
global helper.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2013-06-11 23:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 23:08 [RFC 0/7] Fixing dma mask setting in various network drivers Russell King - ARM Linux
2013-06-10 23:09 ` [PATCH 1/7] NET: brocade/bna/bnad.c: fix 32-bit DMA mask handling Russell King
2013-06-10 23:10 ` [PATCH 2/7] NET: intel/e1000e/netdev.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:11 ` [PATCH 3/7] NET: intel/igb/igb_main.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:12 ` [PATCH 4/7] NET: intel/igbvf/netdev.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:13 ` [PATCH 5/7] NET: intel/ixgb/ixgb_main.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:14 ` [PATCH 6/7] NET: intel/ixgbe/ixgbe_main.c: " Russell King
2013-06-10 23:28 ` Jeff Kirsher
2013-06-10 23:15 ` [PATCH 7/7] NET: intel/ixgbevf/ixgbevf_main.c: " Russell King
2013-06-10 23:28 ` Jeff Kirsher
2013-06-11 18:12 ` [RFC 0/7] Fixing dma mask setting in various network drivers Jesse Brandeburg
2013-06-11 20:35 ` Russell King - ARM Linux
2013-06-11 23:50 ` Jesse Brandeburg [this message]
2013-06-12 0:01 ` Russell King - ARM Linux
2013-06-17 14:01 ` Russell King - ARM Linux
2013-06-17 20:35 ` Jeff Kirsher
2013-06-17 20:45 ` Russell King - ARM Linux
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=20130611165044.00000d3a@unknown \
--to=jesse.brandeburg@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=john.ronciak@intel.com \
--cc=linux@arm.linux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=rmody@brocade.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).