From: Johannes Thumshirn <jthumshirn@suse.de>
To: Max Gurtovoy <maxg@mellanox.com>
Cc: hch@lst.de, sagi@grimberg.me, Keith Busch <keith.busch@intel.com>,
axboe@fb.com, bvanassche@acm.org, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org, vladimirk@mellanox.com
Subject: Re: [PATCH 1/1] blk-mq: map all HWQ also in hyperthreaded system
Date: Wed, 5 Jul 2017 10:15:17 +0200 [thread overview]
Message-ID: <20170705081517.GC4076@linux-x5ow.site> (raw)
In-Reply-To: <fcc21db2-c3fe-48d7-a33a-5eedac00c2bd@mellanox.com>
On Wed, Jul 05, 2017 at 11:11:36AM +0300, Max Gurtovoy wrote:
> Hi Johannes,
> this was merge already to the main tree (Jens add it to his pull request)
Oops, sorry for the noise.
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N�rnberg
GF: Felix Imend�rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N�rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
WARNING: multiple messages have this Message-ID (diff)
From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH 1/1] blk-mq: map all HWQ also in hyperthreaded system
Date: Wed, 5 Jul 2017 10:15:17 +0200 [thread overview]
Message-ID: <20170705081517.GC4076@linux-x5ow.site> (raw)
In-Reply-To: <fcc21db2-c3fe-48d7-a33a-5eedac00c2bd@mellanox.com>
On Wed, Jul 05, 2017@11:11:36AM +0300, Max Gurtovoy wrote:
> Hi Johannes,
> this was merge already to the main tree (Jens add it to his pull request)
Oops, sorry for the noise.
--
Johannes Thumshirn Storage
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2017-07-05 8:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 12:44 [PATCH 1/1] blk-mq: map all HWQ also in hyperthreaded system Max Gurtovoy
2017-06-28 12:44 ` Max Gurtovoy
2017-06-28 13:07 ` Johannes Thumshirn
2017-06-28 13:07 ` Johannes Thumshirn
2017-06-28 14:15 ` Christoph Hellwig
2017-06-28 14:15 ` Christoph Hellwig
2017-06-28 14:38 ` Sagi Grimberg
2017-06-28 14:38 ` Sagi Grimberg
2017-06-28 14:55 ` Max Gurtovoy
2017-06-28 14:55 ` Max Gurtovoy
2017-06-28 15:01 ` Sagi Grimberg
2017-06-28 15:01 ` Sagi Grimberg
2017-06-28 17:11 ` Max Gurtovoy
2017-06-28 17:11 ` Max Gurtovoy
2017-06-29 8:30 ` Johannes Thumshirn
2017-06-29 8:30 ` Johannes Thumshirn
2017-06-28 14:43 ` Guilherme G. Piccoli
2017-06-28 14:43 ` Guilherme G. Piccoli
2017-06-28 14:58 ` Sagi Grimberg
2017-06-28 14:58 ` Sagi Grimberg
2017-06-28 15:09 ` Max Gurtovoy
2017-06-28 15:09 ` Max Gurtovoy
2017-06-29 5:33 ` Sagi Grimberg
2017-06-29 5:33 ` Sagi Grimberg
2017-06-29 14:31 ` Christoph Hellwig
2017-06-29 14:31 ` Christoph Hellwig
2017-07-03 13:38 ` Johannes Thumshirn
2017-07-03 13:38 ` Johannes Thumshirn
2017-07-05 7:59 ` Johannes Thumshirn
2017-07-05 7:59 ` Johannes Thumshirn
2017-07-05 8:11 ` Max Gurtovoy
2017-07-05 8:11 ` Max Gurtovoy
2017-07-05 8:15 ` Johannes Thumshirn [this message]
2017-07-05 8:15 ` Johannes Thumshirn
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=20170705081517.GC4076@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=axboe@fb.com \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=maxg@mellanox.com \
--cc=sagi@grimberg.me \
--cc=vladimirk@mellanox.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 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.