Drive signal in the driver

UVM
1

Hi All, I have a driver, which drive signal A for one cycle, and drive signal B for two cycles.
Because, thread A only spend one clock and seq_item_port will get next req after thread A finish. But,the thread B spend two clocks, so new thread B will start even older thread B not finish . Now I have two questions
Q1:In my code, new thread B will start even older thread B not finish. Am I correct?
Q2: In older thread B, req.b will be changed due to seq_item_port getting new req. it means that the vif.b can not keep stable for two clocks. Am I correct? How to fix this problem?
Thanks a lot!

Here is my code

while(1)begin
seq_item_port.get_next_item(req);
fork
begin // thread A
@(posedge clk);
vif.a <= req.a;
end
begin // thread B
@(posedge clk);
@(posedge clk);
vif.b <= req.b;
end
join_any
seq_item_port.item_done();
end
2

Please format your code and use indentation making your code easier for others to read. I have done that for you.

A1. Yes.
A2. You can make local copies of the req variables you need, or clone the entire req item inside thread B

begin // thread B
  bit b = req.b;
  @(posedge clk);
  @(posedge clk);
  vif.b <= b;
end

Or you can take advantage of the transport delays in a nonblocking assignment and not need a fork/join_any

while(1)begin
  seq_item_port.get_next_item(req);
  @(posedge clk);
  vif.a <= req.a;
  vif.b <= @(posege clk) req.b;
  seq_item_port.item_done();
end
3

As for using transport delays method, why the req.b will not be changed by next req?
thanks