From: David Miller <davem@davemloft.net>
To: tglx@linutronix.de
Cc: bhutchings@solarflare.com, netdev@vger.kernel.org,
linux-net-drivers@solarflare.com, therbert@google.com
Subject: Re: [PATCH net-next-2.6 1/5] genirq: Add IRQ affinity notifiers
Date: Wed, 19 Jan 2011 13:27:30 -0800 (PST) [thread overview]
Message-ID: <20110119.132730.57462002.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.2.00.1101192214350.3211@localhost6.localdomain6>
From: Thomas Gleixner <tglx@linutronix.de>
Date: Wed, 19 Jan 2011 22:19:04 +0100 (CET)
> B1;2401;0cOn Wed, 19 Jan 2011, Ben Hutchings wrote:
>
>> When initiating I/O on a multiqueue and multi-IRQ device, we may want
>> to select a queue for which the response will be handled on the same
>> or a nearby CPU. This requires a reverse-map of IRQ affinity. Add a
>> notification mechanism to support this.
>>
>> This is based closely on work by Thomas Gleixner <tglx@linutronix.de>.
>>
>> Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
>> ---
>> Thomas, I hope this answers all your comments. If you are happy with
>> this, can it go into net-next-2.6 so the rest of this series can get
>> into 2.6.39?
>
> Looks good, but I prefer to take it via the tip/genirq branch as I
> have other changes pending to that code. I'll put this into a separate
> branch based on rc1 as a single commit so Dave can pull that branch
> into netdev. Dave ?
But if you do that what happens down the line when Linus pulls our trees
in?
If he takes your tip/genirq first, I have merge hassles to deal with.
If he takes the -rc1 relative version I end up with, you'll have the
merge hassles.
next prev parent reply other threads:[~2011-01-19 21:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 20:59 [PATCH net-next-2.6 0/5] RFS hardware acceleration (v3) Ben Hutchings
2011-01-19 21:01 ` [PATCH net-next-2.6 1/5] genirq: Add IRQ affinity notifiers Ben Hutchings
2011-01-19 21:19 ` Thomas Gleixner
2011-01-19 21:27 ` David Miller [this message]
2011-01-19 21:39 ` Thomas Gleixner
2011-01-19 21:48 ` David Miller
2011-01-19 21:53 ` Thomas Gleixner
2011-01-22 16:38 ` Thomas Gleixner
2011-02-07 20:44 ` Ben Hutchings
2011-01-24 23:01 ` David Miller
2011-01-19 21:03 ` [PATCH net-next-2.6 2/5] lib: cpu_rmap: CPU affinity reverse-mapping Ben Hutchings
2011-01-24 23:01 ` David Miller
2011-01-19 21:03 ` [PATCH net-next-2.6 3/5] net: RPS: Enable hardware acceleration of RFS Ben Hutchings
2011-01-24 23:01 ` David Miller
2011-01-19 21:06 ` [PATCH net-next-2.6 4/5] sfc: Limit filter search depth further for performance hints (i.e. RFS) Ben Hutchings
2011-01-24 23:02 ` David Miller
2011-01-19 21:06 ` [PATCH net-next-2.6 5/5] sfc: Implement hardware acceleration of RFS Ben Hutchings
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=20110119.132730.57462002.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=therbert@google.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).