On Mon, 2013-06-17 at 22:00 +, Weiny, Ira wrote:
> Does running "update_desc" in the console fix this?
This worked as a short term solution. But we're still thinking about a
longer term one that requires less interaction.
Al
> Ira
>
> > -Original Message-
> > From: linux-rdma-ow...
Loan Syndicacion
Am AFG Guaranty Trust Bank, zu strukturieren wir Kreditlinien treffen Sie
unsere
Kunden spezifischen geschäftlichen Anforderungen und einen deutlichen
Mehrwert für unsere
Kunden Unternehmen.
eine Division der AFG Finance und Private Bank plc.
Wenn Sie erwägen, eine große Akqui
Does running "update_desc" in the console fix this?
Ira
> -Original Message-
> From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-
> ow...@vger.kernel.org] On Behalf Of Albert Chu
> Sent: Monday, June 17, 2013 2:38 PM
> To: linux-rdma@vger.kernel.org
> Subject: Node Description mis
We've recently noticed that the Node Description for a node can
mis-mismatch between the output of smpquery and saquery. For example:
# smpquery NodeDesc 427
Node Description:.sierra1932 qib0
# saquery NodeRecord 427 | grep NodeDesc
NodeDescription.QLogic
Keep IBV_MTU_* enums values as they are, but pass MTU values around as
int's. This is an ABI-compatible change; legacy applications will use
the enum values, but newer applications can use an int for values that
do not currently exist in the enum set (e.g., 1500, 9000).
(if people like the idea o
On 6/16/2013 9:02 AM, Or Gerlitz wrote:
> opensm 3.3.15 comes with /etc/rdma/opensm.conf as part of the rpm,
> 3.3.16 doesn't, why?
I'm not 100% sure about the origin of those RPMs but I think the 3.3.15
one is RedHat packaged and the 3.3.16 appears to be PLD packaged and the
processes are a littl
On Mon, 17 Jun 2013, Peter Zijlstra wrote:
> They did no such thing; being one of those who wrote such code. I
> expressly used RLIMIT_MEMLOCK for its the one limit userspace has to
> limit pages that are exempt from paging.
Dont remember reviewing that. Assumptions were wrong in that patch then.
On Tue, Jun 11, 2013 at 2:42 PM, Or Gerlitz wrote:
[...]
> V0 has been acknowledged by Steve and Christoph, and was also got positive
> feedback from Sean and Jason over f2f talks we had during the Linux
> Foundation EU
> summit on last month.
Hi Roland,
So we're @ -rc6 and there's also other g
On Thu, 13 Jun 2013, Andrew Morton wrote:
> Let's try to get this wrapped up?
>
> On Thu, 6 Jun 2013 14:43:51 +0200 Peter Zijlstra wrote:
>
> >
> > Patch bc3e53f682 ("mm: distinguish between mlocked and pinned pages")
> > broke RLIMIT_MEMLOCK.
>
> I rather like what bc3e53f682 did, actually.
On Fri, Jun 07, 2013 at 02:52:05PM +, Christoph Lameter wrote:
> On Fri, 7 Jun 2013, Peter Zijlstra wrote:
>
> > However you twist this; your patch leaves an inconsistent mess. If you
> > really think they're two different things then you should have
> > introduced a second RLIMIT_MEMPIN to go
On 17.06.2013 09:29, Bart Van Assche wrote:
> On 06/17/13 09:14, Hannes Reinecke wrote:
>> On 06/17/2013 09:04 AM, Bart Van Assche wrote:
>>> I agree that the value of fast_io_fail_tmo should be kept small.
>>> Although as you explained changing the SCSI device state into
>>> SDEV_BLOCK doesn't hel
On Thu, Jun 13, 2013 at 02:06:32PM -0700, Andrew Morton wrote:
> Let's try to get this wrapped up?
>
> On Thu, 6 Jun 2013 14:43:51 +0200 Peter Zijlstra wrote:
>
> >
> > Patch bc3e53f682 ("mm: distinguish between mlocked and pinned pages")
> > broke RLIMIT_MEMLOCK.
>
> I rather like what bc3e53
On 14.06.2013 19:07, Vu Pham wrote:
[...]
>> For what do you need the same target with multiple pkeys on the same
>> local SRP port?
>>
> There is no need, it's just a gray area that you can choose to have
> multiple connections to same target using different pkeys (same as dgid)
>> Which other
On 06/17/2013 09:29 AM, Bart Van Assche wrote:
> On 06/17/13 09:14, Hannes Reinecke wrote:
>> On 06/17/2013 09:04 AM, Bart Van Assche wrote:
>>> I agree that the value of fast_io_fail_tmo should be kept small.
>>> Although as you explained changing the SCSI device state into
>>> SDEV_BLOCK doesn't
On 06/17/13 09:14, Hannes Reinecke wrote:
On 06/17/2013 09:04 AM, Bart Van Assche wrote:
I agree that the value of fast_io_fail_tmo should be kept small.
Although as you explained changing the SCSI device state into
SDEV_BLOCK doesn't help for I/O that has already been queued on a
failed path, I
On 06/17/2013 09:04 AM, Bart Van Assche wrote:
> On 06/17/13 08:18, Hannes Reinecke wrote:
>> On 06/15/2013 11:52 AM, Bart Van Assche wrote:
[ .. ]
>>>
>>> I think the advantage of multipathd recognizing the SDEV_BLOCK state
>>> before the fast_io_fail_tmo timer has expired is important.
>>> Multip
On 06/17/13 08:18, Hannes Reinecke wrote:
On 06/15/2013 11:52 AM, Bart Van Assche wrote:
On 06/14/13 19:59, Vu Pham wrote:
On 06/13/13 21:43, Vu Pham wrote:
+/**
+ * srp_tmo_valid() - check timeout combination validity
+ *
+ * If no fast I/O fail timeout has been configured then the
device
los
17 matches
Mail list logo
