From: Sebastian Riemer <sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Solved: IB/iSER problems with Linux 3.0
Date: Thu, 19 Jan 2012 14:56:22 +0100 [thread overview]
Message-ID: <4F182106.1040002@profitbricks.com> (raw)
In-Reply-To: <4F1809FC.2020908-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On 19/01/12 13:18, Or Gerlitz wrote:
>> [...]
>> Or Gerlitz (4):
>> IB/iser: Fix wrong mask when sizeof (dma_addr_t) > sizeof
>> (unsigned long)
>> IB/iser: Support iSCSI PDU padding
>> IB/iser: Use separate buffers for the login request/response
>> IB/iser: DMA unmap TX bufs used for iSCSI/iSER headers
>> [...]
> could you try only the four of them on top of 3.0.15 and then if it
> works okay, find out which one of them does the job?
I've applied them one by one and at the following commit it worked:
IB/iser: Use separate buffers for the login request/response
Then, I've tried to apply that commit only to 3.0.15, but automatic
cherry-picking failed. I had to apply the following commit first:
IB/iser: Support iSCSI PDU padding
So, these two commits are the winners, for our Solaris 11 COMSTAR targets.
Without them I always had to reboot the system because it wasn't
possible to logout or to unload the ib_iser module.
Cheers,
Sebastian
--
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
prev parent reply other threads:[~2012-01-19 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 21:16 IB/iSER problems with Linux 3.0 Or Gerlitz
[not found] ` <CAJZOPZL=bV4SjdD2eakX9MhOhw=91xzCK=BEkirhRQd8oPA6bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-17 10:26 ` Sebastian Riemer
[not found] ` <4F154CF2.7030504-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2012-01-17 14:56 ` Or Gerlitz
[not found] ` <4F158C0D.7070302-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-01-19 11:29 ` Sebastian Riemer
[not found] ` <4F17FE97.6090708-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2012-01-19 12:18 ` Or Gerlitz
[not found] ` <4F1809FC.2020908-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-01-19 13:56 ` Sebastian Riemer [this message]
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=4F182106.1040002@profitbricks.com \
--to=sebastian.riemer-eikl63zcoxah+58jc4qpia@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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.