From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Anna Schumaker <anna.schumaker@netapp.com>,
linux-rdma <linux-rdma@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v1] xprtrdma: Spread reply processing over more CPUs
Date: Sun, 3 Dec 2017 11:28:44 -0800 [thread overview]
Message-ID: <20171203192844.GB311@infradead.org> (raw)
In-Reply-To: <52245049-E101-4148-8A35-10368379FF20@oracle.com>
On Sun, Dec 03, 2017 at 01:52:28PM -0500, Chuck Lever wrote:
>
> > On Dec 3, 2017, at 1:35 PM, Christoph Hellwig <hch@infradead.org> wrote:
> >
> > Hmm. I'd love to find a way to handle this in the core code, but until
> > that is done you should probably move sc_rq_cq to execture in softirq
> > code.
>
> You mean revert a4699f5647f3 as well? I tried that in combination
> with this change, and it did not result in any difference in
> throughput results.
Ok. I guess we can leave things as-is for now then.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Anna Schumaker
<anna.schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux NFS Mailing List
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v1] xprtrdma: Spread reply processing over more CPUs
Date: Sun, 3 Dec 2017 11:28:44 -0800 [thread overview]
Message-ID: <20171203192844.GB311@infradead.org> (raw)
In-Reply-To: <52245049-E101-4148-8A35-10368379FF20-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
On Sun, Dec 03, 2017 at 01:52:28PM -0500, Chuck Lever wrote:
>
> > On Dec 3, 2017, at 1:35 PM, Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> wrote:
> >
> > Hmm. I'd love to find a way to handle this in the core code, but until
> > that is done you should probably move sc_rq_cq to execture in softirq
> > code.
>
> You mean revert a4699f5647f3 as well? I tried that in combination
> with this change, and it did not result in any difference in
> throughput results.
Ok. I guess we can leave things as-is for now then.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-12-03 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 21:31 [PATCH v1] xprtrdma: Spread reply processing over more CPUs Chuck Lever
2017-12-02 21:31 ` Chuck Lever
2017-12-03 18:35 ` Christoph Hellwig
2017-12-03 18:35 ` Christoph Hellwig
2017-12-03 18:52 ` Chuck Lever
2017-12-03 18:52 ` Chuck Lever
2017-12-03 19:28 ` Christoph Hellwig [this message]
2017-12-03 19:28 ` Christoph Hellwig
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=20171203192844.GB311@infradead.org \
--to=hch@infradead.org \
--cc=anna.schumaker@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.